Facility ID inference method and facility ID inference device

Abstract

To infer a facility XID, a connection destination facility, a belonging destination facility, and a boundary facility.SOLUTION: A facility ID inference device comprises: a facility XID candidate generation unit 542 which derives data groups or combination of the data groups in which overlap of data do not exist as facility XID candidates for every type of power facilities; a facility XID inference unit 543 which narrows down the facility XID candidates to a facility XID partially coincident with facility XID candidates in other type of power facility; a belonging destination facility inference unit 544 which infers the facility XID in other type of the power facility included in the facility XID as a belonging destination facility; a connection destination facility inference unit 545 which infers data existing in the same line as that of the facility XID and including a part of the facility XID of other type of the power facility as a connection destination facility; and a boundary facility inference unit 552 which infers the connection destination facility existing in the same line as that of the facility XID as a connection destination facility, and a power facility whose data except the belonging destination facility coincides as a boundary facility in each piece of individual system facility data.SELECTED DRAWING: Figure 5

Description

[Technical field]

[0001] The present invention relates to a facility ID inference method and a facility ID inference device. [Background technology]

[0002] As an example, the present invention relates to an equipment ID inference method and device for assigning an eXplainable ID (XID) to power equipment, which can uniquely identify the power equipment in the entire system data and also explain its connections and affiliations, by inferring an ID system from the name and attribute values ​​of the power equipment, and the power equipment IDs, affiliation IDs, and connection IDs assigned by the power system managers using different ID systems, for the purpose of integrating equipment data of power equipment and its affiliations and connection destinations managed by multiple power system managers in tables consisting of rows and columns under different ID systems to compose entire system data that shows the entire power system in an electric power system represented by the affiliation and connection relationships between power equipment.

[0003] Patent Document 1 describes a technology for identifying a data group corresponding to a data group used in arithmetic processing from among multiple data groups, with the aim of identifying a data string that meets a specific condition for data managed in a table consisting of rows and columns. This publication describes the following: "Acquire multiple data groups each including multiple values ​​corresponding to a data item, identify the number of types of multiple values ​​included in the data group for each of the multiple data groups, acquire a result of arithmetic processing using multiple values ​​included in a specific data group from among the multiple data groups, identify the number of types of multiple values ​​included in the specific data group, select a data group from the multiple data groups based on the number of types of multiple values ​​included in the specific data group and the number of types of multiple values ​​included in each of the multiple data groups, and identify a data group corresponding to the specific data group from the selected data groups based on a correlation between the values ​​included in the selected data group and the values ​​included in the specific data group." [Prior art documents] [Patent documents]

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

[0005] In Patent Document 1, a data group that meets a specific condition is searched for based on the correlation between data groups. By using this correlation, it is possible to derive candidates for power equipment data groups that indicate power equipment in the entire system data, its affiliated equipment, and connected equipment for power equipment data groups with different ID systems. For example, if the correlation between a specific data group and its own data group is one-to-one, that is, if there is no overlap in its own data group, it is possible to estimate the power equipment as a candidate for a power equipment ID that can uniquely identify the power equipment. If there is a one-to-many correlation between this estimated power equipment ID group and a power equipment ID group of a different type, it is possible to estimate the affiliated equipment, one of which is a parent equipment and the other is a child equipment.

[0006] However, there is a possibility that the wrong power equipment ID, the belonging equipment, and the connected equipment are estimated only based on the correlation between data groups. For example, if a specific power equipment data includes a data group of maintenance work completion times that all have different values, this may be erroneously estimated as a power equipment ID because the correlation within the data group is one-to-one. Furthermore, if the same maintenance work completion time is registered in power equipment data managed by different power system managers, there is a possibility that the power equipment with the same maintenance work completion time may be erroneously estimated as being in a connection relationship even if they are not in an affiliation or connection relationship. In addition, for equipment such as power equipment whose layout is widely dispersed, it is difficult to manage it in a single management department, so the equipment to be managed may be divided into a specific range. In this case, in order to manage the connection relationship of the power system, the boundary equipment that exists at the boundary when it is divided is managed with different ID systems at both the division source and the division destination. If the connection relationship is erroneously estimated for this boundary equipment, the same boundary equipment may be considered as different boundary equipment, and the entire system data may not be constructed.

[0007] The present invention has been made in consideration of the above problems, and aims to provide an equipment ID inference method and equipment ID inference device that are capable of creating entire system data representing the entire power system by inferring equipment XIDs, connected equipment, affiliated equipment, and boundary equipment for individual system equipment data of different ID systems. [Means for solving the problem]

[0008] In order to solve the above problem, an equipment ID inference method according to one aspect of the present invention is an equipment ID inference method that identifies electric power equipment from individual system equipment data that is managed in a table for each type of electric power equipment using a different ID system for each part of the electric power system, and infers an equipment XID that is unique in the entire electric power system, an equipment to which the electric power equipment is connected, an equipment to which the electric power equipment belongs, and a boundary equipment that is managed in a duplicated manner in multiple individual system equipment data, and includes an equipment XID derivation step of deriving a data group or a combination of data groups that does not have data duplication for each type of electric power equipment as an equipment XID candidate based on the individual system equipment data managed in the same ID system, and a step of comparing the equipment XID candidate with other types of electric power equipment in the individual system equipment data managed in the same ID system. the equipment XID inference procedure narrows down the equipment XIDs to those that partially match the equipment XID candidates in the equipment XID list; an affiliated equipment inference procedure for inferring, in individual system equipment data managed with the same ID system, an equipment XID of another power equipment type included in the equipment XID as the affiliated equipment; a destination equipment inference procedure for inferring, in individual system equipment data managed with the same ID system, data that exists in the same row as the equipment XID and includes part of the equipment XID of the other power equipment type as the destination equipment; and a boundary equipment inference procedure for inferring, based on a plurality of individual system equipment data managed with different ID systems, power equipment that exists in the same row as the equipment XID in each individual system equipment data and has matching data other than the affiliated equipment as the boundary equipment. Effect of the Invention

[0009] According to the present invention, it is possible to realize an equipment ID inference method and equipment ID inference device that can create entire system data representing the entire power system by inferring equipment XIDs, connected equipment, affiliated equipment, and boundary equipment for individual system equipment data of different ID systems. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating an example of individual system equipment data related to bus equipment, which is used in the equipment ID inference device of the first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of individual system equipment data related to connected equipment, which is used in the equipment ID inference device of the first embodiment. [Diagram 3] FIG. 2 is a diagram showing an example of a facility ID inference result by the facility ID inference device of the first embodiment. [Figure 4] FIG. 2 is a diagram showing an example of a boundary facility inference result by the facility ID inference device of the first embodiment. [Diagram 5] FIG. 1 illustrates a facility ID estimation device according to a first embodiment. [Figure 6] 1 is a flowchart showing an equipment XID inference process according to the equipment ID inference method of the first embodiment. [Figure 7] 11 is a flowchart showing a destination facility XID inference process according to the facility ID inference method of the first embodiment. [Figure 8] 11 is a flowchart showing a destination equipment XID inference process according to the equipment ID inference method of the first embodiment. [Figure 9] 11 is a flowchart showing a boundary facility inference process according to the facility ID inference method of the first embodiment. [Figure 10] FIG. 2 is a diagram illustrating an example of individual system equipment data related to substation equipment, which is used in the equipment ID inference device of the first embodiment. [Figure 11] FIG. 11 is a diagram illustrating a facility ID inference device according to a second embodiment. [Figure 12] 13 is a flowchart showing an analysis file generation process by the facility ID inference method according to the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The following description and drawings are examples for explaining the present invention, and appropriate omissions and simplifications have been made for clarity of explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural.

[0012] In the drawings explaining the embodiments, the same reference numerals are used to designate parts having the same functions, and repeated explanations thereof will be omitted.

[0013] In order to facilitate understanding of the invention, the position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings.

[0014] In the following explanation, various information may be explained using expressions such as "table," "list," and "queue," but the various information may be expressed in other data structures. To indicate independence of data structure, "XX table," "XX list," and the like may be referred to as "XX information." When explaining identification information, expressions such as "identification information," "identifier," "name," "ID," and "number" are used, but these are interchangeable.

[0015] Furthermore, in the following description, the configuration of each table is an example, and one table may be divided into two or more tables, or all or part of two or more tables may be one table.

[0016] When there are multiple components having the same or similar functions, they may be described by using the same reference numerals with different subscripts, but when there is no need to distinguish between these multiple components, the subscripts may be omitted.

[0017] The facility ID inference device of this embodiment has, as an example, the following configuration.

[0018] In this embodiment, power equipment data managed by different ID systems for each power system manager is input. First, for a data group included in the power equipment data, if there is no duplicate data in the data group, a candidate equipment ID and a data group having some correspondence with the candidate equipment ID are derived as connection destination and affiliation candidates. Then, by determining whether the data group of the connection destination and affiliation candidates matches the candidate equipment ID as an actual facility, a data group that can be used to uniquely identify the facility in the power equipment data and identify the affiliated power equipment and the connected power equipment is extracted. The purpose is to infer the equipment ID of the extracted data group and assign it to the power equipment as an eXplainable ID (XID) that can uniquely identify the power equipment in the entire system data and explain its connection destination and affiliation.

[0019] In order to solve the above problem, the present invention provides a method for inferring equipment XIDs, connected equipment XIDs, belonging XIDs, and overlapping equipment to constitute the entire system for individual system equipment data managed in tables for each equipment type in different ID systems for each part of the power system, the method comprising: a means for deriving, as equipment XID candidates, data groups or combinations of data groups in which there is no data overlap for each equipment type in the same ID system; an equipment XID inference means for narrowing down the equipment XID candidates to equipment XIDs that partially match equipment XID candidates of other equipment types in the same ID system; a means for inferring, in the same ID system, an equipment XID of another equipment type included in the equipment XID as a belonging XID; a means for inferring, in the same ID system, data that exists in the same row as the equipment XID and includes part of the equipment XID of the other equipment type as a connected equipment XID; and a means for inferring, in a different ID system, equipment that exists in the same row as the equipment XID and has matching data other than the connected equipment XID and belonging XID as a boundary equipment.

[0020] According to this embodiment, even when multiple individual system equipment data management devices manage equipment that constitutes part of the power system using different ID systems, information for constructing system-wide data, which is the entire power system including the affiliation and connection relationships between equipment, can be obtained by an equipment ID inference device that infers the equipment XID, affiliation XID, connection destination XID, and boundary equipment. EXAMPLES

[0021] In this embodiment, first, an example of facility ID inference is described in which a facility XID uniquely indicating a facility for each part of the power system, a facility's affiliation XID, a facility's connection destination XID, and a boundary facility that is managed in duplicate with different ID systems are inferred from individual system facility data with an unknown ID system, with the aim of configuring an entire system that indicates the entire power system from power facility data managed in individual tables for each part. Then, an example of a facility ID inference device is described.

[0022] 1, 2, and 10 show examples of individual system equipment data managed in tables.

[0023] Figure 1 shows data related to busbar equipment, Figure 2 shows data related to connection equipment, and Figure 10 shows data related to substations. In the data shown in Figures 1, 2, and 10, the data item name is written on the first line (101, 201, 1001), and data indicating each system equipment is written on the second and subsequent lines.

[0024] 1, in the case of an ID system that uniquely identifies equipment in an individual system by a combination of management codes, the equipment ID is indicated by a combination of management code 1 102 and management code 2 103, Tr-1-Bs-1. This is an XID that also explains the affiliation relationship, that is, equipment number 1 of equipment type Bs belongs to equipment type Tr number 1.

[0025] The combination Tr-1-Ln-1 in Fig. 2 is an equipment XID indicating equipment of equipment type Ln number 1 belonging to equipment type Tr number 1. Among other item names, name 104, attribute 1 105, and attribute 2 106 are attribute values ​​of each equipment. Power transmission destination 107 indicates a connected equipment that is a connection destination of the bus equipment managed in the table in Fig. 1. The data described is a part of the equipment XID of the connection destination, such as Ln-1 or Ln-2.

[0026] In the example table of FIG. 1, there is a destination facility for the connection to management code 1 102, and by combining this, it can be inferred that the destination XID of the facility with facility XID Tr-1-Bs-1 is Tr-1-Ln-1, for example.

[0027] Figure 3 shows an example of facility ID inference results, in which the inferred results of the above facility XID, affiliated facility XID, and connected facility XID are added to the example of individual system facility data in Figure 1. Facility XID301, affiliated facility XID302, and connected facility XID303, which can explain the facility affiliation, have been added to the table.

[0028] After inferring the equipment ID of this individual system equipment data with an unknown ID system, inference is performed on the boundary equipment to integrate the individual system equipment data to configure the entire system. Here, boundary equipment refers to electric power equipment that is managed in duplicate in multiple individual system equipment data. An example of the data used in inferring the boundary equipment is shown in Figure 4.

[0029] FIG. 4 shows the facility ID inference result (FIG. 4(a)) and the facility ID inference result (FIG. 4(b)) when facility ID inference is performed on individual system facility data of different parts. Each facility XID is assigned in a different ID system, and a match between them does not allow the facility to be identified as a boundary facility. Therefore, the facility ID inference result shown in FIG. 4(b) is searched for facilities that match the facility XID and attribute values ​​401 such as name 104, attribute A 105, and attribute B 106, which are information other than the facility XID and the information used for the inference, for the facility ID inference result shown in FIG. 4(a). As a result, the facility with facility XID 402 of Tr-2-Bs-1 in the facility ID inference result in FIG. 4(b) can be inferred as a boundary facility.

[0030] In the following, an example of a facility ID inference device that infers the facility XID, the affiliated facility XID, the connected facility XID, and the boundary facility shown in the examples of Figures 1 to 4 from individual system facility data will be described.

[0031] FIG. 5 shows an example of the configuration of a facility ID inference device that provides the facility ID inference method in this embodiment.

[0032] The equipment ID inference device 501 infers equipment XID, affiliated equipment XID, connected equipment XID, and boundary equipment based on the individual system equipment data shown in Fig. 1 and Fig. 2, which are managed by a plurality of individual system equipment data management devices 502 and constitute a part of the power system. This makes it possible to configure an entire system consisting of all the power equipment included in the power system and their relationships.

[0033] The facility ID inference device 501 of this embodiment can be realized using a general computer equipped with a storage device 511 such as a hard disk, a CPU 512, a memory 513, a communication device 514, a display device 515, and an input device 516.

[0034] The communication device 514 exchanges various data and commands with other devices via a LAN (Local Area Network) etc. The display device 515 is a display or the like, and displays the execution status and execution results of the processing by the facility ID inference device 501. The input device 516 is a device for inputting instructions to the computer, such as a keyboard or mouse, and inputs instructions such as program startup.

[0035] The storage device 511 stores a program 521 for executing the equipment ID inference device 501, inference rules 522 for inferring the XID of the equipment, attribute value collection conditions 523 for collecting attribute values ​​associated with the equipment other than the equipment XID, the equipment XID to which the equipment belongs, and the equipment XID to which the equipment is connected from the power equipment data managed by the individual system equipment data management device 502, and equipment information not managed in a table 524 for inferring an equipment ID using equipment information not managed in a table.

[0036] The memory 513 holds a program 521 that the facility ID inference device 501 uses to execute processing.

[0037] The CPU 512 reads out the program 521 and various data stored in the storage device 511 into the memory 513 and executes them. The program 521 includes an individual system equipment XID inference unit 531 and an overall system equipment inference unit 532. The individual system equipment XID inference unit 531 is composed of an individual system equipment data collection unit 541, an equipment XID candidate generation unit 542, an equipment XID inference unit 543, an affiliated equipment XID inference unit 544, and a connected equipment XID inference unit 545. The overall system equipment inference unit 532 is composed of an attribute value collection unit 551 and a boundary equipment inference unit 552.

[0038] 6 is a process flow for inferring an equipment XID that can explain the equipment type and affiliation relationship from a code included in the character string of the individual system equipment data managed by the individual system equipment data management device 502 using the inference rule 522. Details of this process flow will be described below.

[0039] First, the individual system equipment data collection unit 541 collects individual system equipment data managed in a table for each equipment type as shown in Fig. 1 and Fig. 2 from a plurality of individual system equipment data management devices 502 via a communication device (process 601). After that, the equipment XID candidate generation unit 542 reads data groups of each column of the individual system equipment data managed in a table (process 602) and checks whether or not there is duplicate data in the column data group (process 603). If there is no column data group that does not contain duplicate data, the process proceeds to process 604. If there is a column data group that does not contain duplicate data, the column data group is set as an equipment XID candidate and the process proceeds to process 605.

[0040] In process 604, a combination of multiple column data groups is treated as a column data group, and the process returns to checking for duplicate data in process 603. In this process flow, the first time process 604 is executed, the number of column data groups to be combined is increased according to the number of times, to a combination of two column data groups, and the second time to a combination of three column data groups.

[0041] A combination of column data groups is a data group such as Tr-1-Bs-1, Tr-1-Bs-2, Tr-2-Bs-1, or a data group such as Tr-1-AAA equipment, Tr-1-BBB equipment, Tr-2-CCC equipment, in the case of the individual system equipment data illustrated in Fig. 1. Note that if there is a table row in which all data is duplicated, it is not possible to create a combination of column data groups that does not contain duplicate data, so that table row is excluded from the duplication determination in process 603, or it may be deleted at the time of data collection in process 601.

[0042] In process 605 and after, the equipment XID inference unit 543 receives the equipment XID candidates generated for each equipment type as input, and infers an equipment XID that can explain the equipment type and affiliation.

[0043] In process 605, the rate at which the equipment XID candidates generated for each equipment type partially match with equipment XID candidates of different types is derived. Specifically, if the equipment XID candidates Tr-1-Bs-1, Tr-1-Bs-2, and Tr-2-Bs-1 related to bus equipment generated from Fig. 1 are the equipment XID candidates Tr-1 and Tr-2 related to substation equipment, the equipment XID candidates Tr-1 and Tr-2 related to substation equipment are both partially matched with the equipment XID candidates Tr-1-Bs-1, Tr-1-Bs-2, and Tr-2-Bs-1 related to the partial match. In this case, it can be said that the equipment XID candidates related to bus equipment partially match with the equipment XID candidates related to substation equipment at a rate of 100%.

[0044] After performing the process of deriving the partial match rate, in process 606, an equipment XID candidate with a partial match rate of 100% is inferred to be the equipment XID of that type. If there is no equipment XID candidate with a partial match rate of 100%, it is displayed as exceptional data on display device 515. If there are multiple equipment XID candidates with a partial match rate of 100%, the equipment XIDs may be displayed on display device 515 and then the user may be allowed to select an equipment XID via the input device, or an equipment XID candidate composed of a column data group present in an earlier column in the table may be inferred to be the equipment XID of that type.

[0045] In addition, if there is equipment data that is not managed by the individual system equipment data management device 502, the equipment data may be stored in the table non-managed equipment information 524 by adding the management code 102 or management code 103 shown in Figure 1 to the equipment data, and a process may be added in the processing flow of Figure 6 in which the individual system equipment data collection unit 541 collects the equipment data, or the user may input the equipment data via an input device.

[0046] 7 shows a process flow in which, after inferring the equipment XID, the destination equipment XID inference unit 544 infers the destination equipment XID using the equipment XID and the information of the equipment XID that partially matches. The details of this process flow will be described below.

[0047] First, in process 701, the affiliated equipment XID inference unit 544 receives the equipment XID inference results for each equipment type and the equipment XIDs that are partial matches of the equipment XIDs for each equipment type. In process 702, it is confirmed whether the number of types of equipment XIDs that are partial matches of the equipment XID is 1 or more. If it is not 1 or more, the process proceeds to process 703, and if it is 1 or more, the process proceeds to process 704.

[0048] In process 703, it is determined that the equipment XID of the corresponding equipment type does not belong to any other equipment, and the process is terminated. In process 704, the number of equipment XIDs that partially match is checked, and the equipment XID with the largest number of equipment XIDs that partially match is inferred to be the equipment XID that belongs to, and the process is terminated.

[0049] Fig. 8 shows a process flow in which, after inferring the equipment XID and the destination equipment XID, the destination equipment XID inference unit 545 infers the destination equipment XID using the equipment XID, the destination equipment XID, and the individual system equipment data for each equipment type shown in Fig. 1 and Fig. 2. Details of this process flow will be described below.

[0050] First, in process 801, the individual system equipment data for each equipment type is searched for a sequence data group including an equipment XID of the equipment type itself or an equipment XID of the equipment to which it belongs. Then, in process 802, the sequence data group excluding the searched sequence data group is set as a connection destination candidate sequence data group, and a sequence data group including a part of an equipment XID of an equipment type other than the own is searched for. As a result of this search, the process branches depending on whether or not a corresponding connection destination candidate sequence data group exists (process 803). If it exists, the process proceeds to process 804, and if it does not exist, it is determined that the connection destination equipment XID does not exist and the process ends (process 810).

[0051] In process 804, it is confirmed whether there is even one character string in the connection destination candidate sequence data group that completely matches the equipment XID of another equipment type (process 805). If there is, the process proceeds to process 809, and if not, the process proceeds to process 806. In process 806, a combined connection destination candidate sequence data group is generated by combining the connection destination candidate sequence data group with a portion of the affiliated equipment in the own equipment type.

[0052] Then, in process 807, it is confirmed whether or not there is even one character string in this combined connection destination candidate sequence data group that completely matches an equipment XID of another equipment type. If there is, the process proceeds to process 809, and if there is not, the process proceeds to process 810 (process 808). In process 809, the connection destination candidate sequence data group or the combined connection destination candidate sequence data group that contains a character string that completely matches an equipment XID of another equipment type is inferred to be the connection destination equipment XID, and the process ends.

[0053] 9 shows a process flow for inferring a boundary facility, which is an electric power facility that is managed in a redundant manner by a plurality of individual system equipment data management devices 502, by using the inference results of different individual system equipment data management devices 502, individual system equipment data, and attribute value collection conditions 523 after inferring the facility XID, the affiliated facility XID, and the connected facility XID. Details of this process flow will be described below.

[0054] In process 901, attribute value collection unit 551 extracts an attribute value group associated with the power facility from the individual system facility data using the inference result and attribute value collection condition 523. Specifically, among column data groups that do not include the inferred facility XID, the affiliated facility XID, and the connected facility XID, a column data group that matches the condition described in attribute value collection condition 523 is set as an attribute value group. The condition described in attribute value collection condition 523 may be a keyword included in a column name, or may be a characteristic of the data included in the column data group, such as a numerical value or a symbol.

[0055] In process 902, the boundary facility inference unit 552 generates facility attribute information consisting of a pair of the facility XID and an attribute value existing in the same row on the individual system facility data. Then, in process 903, facility attribute information having a matching attribute value, which is facility attribute information other than the facility XID, is searched from all the individual system facility data managed by different individual system facility data management devices 502.

[0056] In process 904, the process branches depending on whether the attribute values ​​match. If facility attribute information with matching attribute values ​​exists, the facility with that attribute value is inferred to be a boundary facility, and the process ends (process 905). If not, it is determined that no boundary facility exists, and the process ends (process 906). Here, the match of attribute values ​​is not limited to an exact match in character strings, but a so-called semantic match, which allows for variations in notation, will suffice.

[0057] According to this embodiment, even when multiple individual system equipment data management devices 502 manage power equipment that constitutes part of the power system using different ID systems, the equipment ID inference device 501 of this embodiment, which infers the equipment XID, affiliation XID, connection destination XID, and boundary equipment, can obtain information for constructing the entire system, which is the entire power system including the affiliation and connection relationships between the equipment. EXAMPLES

[0058] In this embodiment, an example is shown in which the facility ID inference device 501 shown in FIG. 5 of the first embodiment is used to infer the facility XID, the facility XID, the connection XID, and the boundary facility, and the entire system data is constructed, and then an analysis file is generated for performing a structural analysis and a power flow analysis of the power system from the relationships between the power facilities.

[0059] These whole system analysis files for various analyses must express the configuration of the power system, including the connections, using only specific power equipment and specific attribute values ​​according to the purpose of the analysis and the requirements of the analysis system. For example, in structural analysis, an analysis file is generated for substation equipment, transmission equipment, and their connections. In this generation, since the substation equipment is not directly connected to the transmission equipment, but is directly connected to the intake equipment belonging to the substation equipment, a process is required to convert the substation equipment and transmission equipment into a logical connection.

[0060] By implementing this conversion process, it will be possible to perform structural analysis to determine the fault tolerance of a power system by tracing the connections in the entire system data and counting the number of unique routes from a specific piece of power equipment to another piece of power equipment, as well as power flow analysis to simulate the flow of electricity by treating the power system as a giant electrical circuit.

[0061] FIG. 11 shows an example of the configuration of a facility ID inference device 501 that generates analysis files used in structural analysis and power flow analysis.

[0062] The facility ID inference device 501 of this embodiment is a device in which an analysis file generation unit 1131 consisting of a node conversion unit 1141, an edge conversion unit 1142, a graph contraction unit 1143, an attribute value collection unit 1144, and a file writing unit 1145 is added to the configuration of the facility ID inference device 501 of Figure 5.

[0063] This analysis file generation unit 1131 receives as input the entire system data after ID inference, the analysis equipment type 1121, and the analysis attributes 1122, and generates an analysis file according to the analysis purpose according to the analysis file generation process flow shown in Fig. 12. The analysis equipment type 1121 and the analysis attributes are the equipment type and attribute value type required depending on the analysis purpose, and may be stored in the storage device 511 and selected by the user, or may be input by the user via the input device 516. Details of this process flow will be described below.

[0064] First, in process 1201, the node conversion unit 1141 generates node data having the equipment XID as the ID for all the system data subjected to ID inference in the embodiment 1. After that, in process 1202, the edge conversion unit 1142 searches for a pair of node IDs having a connection relationship from the destination XID, and generates edge data that holds the pair as FromID and ToID.

[0065] Next, in process 1203, the graph contraction unit 1143 receives the analysis facility type 1121, and sets the node data corresponding to that facility type as the analysis target node data. Next, for all edge data, it is confirmed whether both the FromID and ToID indicate the analysis target node data (process 1204). If both are not the analysis target node data, the process proceeds to process 1206, and if they are the analysis target node data, the process proceeds to process 1210 (process 1205).

[0066] In process 1206, for the FromID and ToID that are not the analysis target node data, the node data to which they belong is searched for by their destination XID. If the destination node data exists, the process proceeds to process 1208, and if not, the process proceeds to process 1209 (process 1207).

[0067] In process 1208, the FromID or ToID is converted into the ID of the searched-for belonging node data, and the process proceeds to process 1204. In process 1209, it is determined that the connection relationship is not the subject of analysis, and the edge data is deleted, and the process ends.

[0068] In process 1210, the attribute value collection unit 1144 receives the edge data and the node data that does not have edge data that is not connected to the analysis target node data as contracted graph type whole system data. After that, in process 1211, the attribute value collection unit 1144 receives the analysis attribute, collects attribute values ​​to be used for analysis from the power equipment data with ID inference, and registers them as attribute values ​​in the node data with a matching ID. In process 1212, the node data with ID and attribute value and the edge data with FromID and ToID are written to a file, and the process ends.

[0069] Through the above processing, even if there is no direct connection between the equipment types required for analysis, but there is a connection between the equipment that belongs to them, it is possible to generate an analysis file that expresses the logical connection between the equipment required for analysis and enables structural analysis and power flow analysis of the power system.

[0070] The present invention is not limited to the above-mentioned embodiment, and various modifications are included. For example, the above-mentioned embodiment has been described in detail to easily explain the present invention, and is not necessarily limited to those having all the configurations described. It is also possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. It is also possible to add, delete, or replace a part of the configuration of each embodiment with another configuration. In addition, each of the above-mentioned configurations, functions, processing units, processing means, etc. may be realized by hardware, for example, by designing them as integrated circuits. In addition, each of the above-mentioned configurations, functions, etc. may be realized by software by a processor interpreting and executing a program that realizes each function. Information such as a program, table, file, etc. that realizes each function can be placed in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD.

[0071] Furthermore, the program code for realizing the functions described in this embodiment can be implemented in a wide range of program or script languages, such as assembler, C / C++, perl, Shell, PHP, Java (registered trademark), and Python.

[0072] In the above-mentioned embodiment, the control lines and information lines are shown as those considered necessary for the explanation, and not all the control lines and information lines are shown in the product. All the components may be connected to each other. [Explanation of symbols]

[0073] 501...Facility ID inference device 502...Individual system equipment data management device 521...Program 522...Inference rule 523...Attribute value collection condition 524...Table non-managed equipment information 531...Individual system equipment XID inference unit 532...All-system equipment inference unit 541...Individual system equipment data collection unit 542...Facility XID candidate generation unit 543...Facility XID inference unit 544...Belonging equipment XID inference unit 545...Connected equipment XID inference unit 551...Attribute value collection unit 552...Boundary equipment inference unit 1121...Facility type 1122...Attribute 1131...Analysis file generation unit 1141...Node conversion unit 1142...Edge conversion unit 1143...Graph contraction unit 1144...Attribute value collection unit 1145...File writing unit

Claims

1. A facility ID inference method for identifying an electric power facility from individual system facility data managed in a table for each type of electric power facility using a different ID system for each part of an electric power system, and inferring a facility XID unique to the entire electric power system, a facility to which the electric power facility is connected, a facility to which the electric power facility belongs, and a boundary facility that is managed in a duplicate manner in a plurality of the individual system facility data, an equipment XID derivation step of deriving a data group or a combination of data groups in which there is no data duplication for each type of power equipment as an equipment XID candidate based on the individual system equipment data managed by the same ID system; an equipment XID inference procedure for narrowing down the equipment XID candidates to the equipment XIDs that partially match the equipment XID candidates in the type of other electric power equipment in the individual system equipment data managed by the same ID system; a destination facility inference step of inferring that the facility XID in the type of another power facility included in the facility XID is the destination facility in the individual system facility data managed by the same ID system; a connection destination facility inference step of inferring that data that exists in the same row as the facility XID and includes a part of the facility XID of a type of another electric power facility in the individual system facility data managed by the same ID system is the connection destination facility; a boundary facility inference step of inferring, based on a plurality of individual system facility data managed by different ID systems, that the power facility that is present in the same row as the facility XID in each of the individual system facility data and that matches data other than the connection destination facility and the belonging facility is the boundary facility; A facility ID inference method comprising:

2. In the step of inferring the destination equipment, an XID of the destination equipment is inferred; In the destination facility inference step, a destination facility XID of the destination facility is inferred.

2. The facility ID inference method according to claim 1 .

3. The equipment ID inference method described in claim 1, characterized in that it includes a procedure for inferring the equipment XID including the XID of the equipment included in the non-table management equipment information by registering an equipment XID candidate for the power equipment for non-table management equipment information that is not managed in the table as one of the types of power equipment.

4. 2. The facility ID inference method according to claim 1, further comprising the step of collecting attribute values ​​other than the belonging facility and the connected facility that match an attribute value collection condition and correspond to the facility XID.

5. 2. The facility ID inference method according to claim 1, wherein in the boundary facility inference step, the power facility having data other than the connected facility and the affiliated facility that partially matches is inferred as the boundary facility.

6. The facility ID inference method according to claim 1, characterized in that it comprises a step of generating an analysis file including a facility structure in which the power facility to which the facility XID has been assigned is node data, the connection between the power facility indicated by the facility XID and the connected facility is edge data, and the attribute values ​​of the power facility are attribute values ​​of the node data.

7. A step of narrowing down the node data indicating the electric power facility to analysis target node data according to an analysis purpose; When the edge data is connected to the node data other than the node data to be analyzed, searching for the node data to which the edge data belongs and which is the node data to be analyzed, by the belonging equipment; A step of changing a connection destination of the edge data to the searched node data; 7. The facility ID inference method according to claim 6, further comprising:

8. An equipment ID inference device that identifies an electric power facility from individual system equipment data that is managed in a table for each type of electric power facility using a different ID system for each part of an electric power system, and infers an equipment XID that is unique in the entire electric power system, a connected equipment of the electric power facility, an equipment to which the electric power facility belongs, and a boundary equipment that is managed in a duplicated manner in a plurality of the individual system equipment data, an equipment XID candidate generation unit that derives a data group or a combination of data groups that does not include data duplication for each type of power equipment as an equipment XID candidate based on the individual system equipment data managed by the same ID system; an equipment XID inference unit that narrows down the equipment XID candidates to the equipment XIDs that partially match the equipment XID candidates in the type of other electric power equipment in the individual system equipment data managed by the same ID system; a destination equipment inference unit that infers that the equipment XID in the type of another electric power equipment included in the equipment XID is the destination equipment in the individual system equipment data managed by the same ID system; A connection destination equipment inference unit that infers that data that exists in the same row as the equipment XID and includes a part of the equipment XID of a type of another electric power equipment in the individual system equipment data managed by the same ID system is the connection destination equipment; a boundary facility inference unit that infers, based on a plurality of individual system facility data managed by different ID systems, as the boundary facility, the power facility that is present in the same row as the facility XID in each of the individual system facility data and that matches data other than the connection destination facility and the belonging facility; A facility ID inference device comprising:

9. The destination equipment inference unit infers the destination equipment XID of the destination equipment, The destination equipment inference unit infers the destination equipment XID of the destination equipment.

9. The facility ID inference device according to claim 8.

10. The equipment ID inference device of claim 8, characterized in that the equipment XID inference unit infers the equipment XID including the XID of the equipment information not managed in the table by registering equipment XID candidates for the power equipment for equipment information not managed in the table that is not managed in the table as one of the types of the power equipment.

11. The facility ID inference device according to claim 8, further comprising an attribute value collection unit that collects attribute values ​​other than the belonging facility and the connected facility that match an attribute value collection condition and correspond to the facility XID.

12. The facility ID inference device according to claim 8 , wherein the boundary facility inference unit infers, as the boundary facility, the electric power facility having data that partially matches data other than the connected facility and the affiliated facility.

13. The facility ID inference device according to claim 8, further comprising an analysis file generation unit that generates an analysis file including an equipment structure in which the power equipment to which the equipment XID has been assigned is node data, the connection between the power equipment indicated by the equipment XID and the connected equipment is edge data, and attribute values ​​of the power equipment are attribute values ​​of the node data.

14. The analysis file generation unit A means for narrowing down the node data indicating the electric power facility to analysis target node data according to an analysis purpose; a means for searching, when the edge data is connected to node data other than the node data to be analyzed, the node data to which the edge data belongs and which is the node data to be analyzed, by the belonging equipment; A means for changing a connection destination of the edge data to the searched node data; 14. The facility ID inference device according to claim 13, further comprising:

Images