JP4519165B2 - Power failure information management system and power failure information management method - Google Patents

Description

  The present invention relates to a power failure information management system that inputs and manages information about a power failure.

Conventional power outage information management system (power outage information management equipment) receives power outage data (power outage section information) from a distribution automation system that performs monitoring and control related to power supply, and sequentially executes processes corresponding to power outage data (patents) Reference 1).
JP-A-7-227042

  However, if an accidental power outage occurs and a large number of power outage data is received from the distribution automation system, the DB update process corresponding to the power outage data is congested in the power outage information management system, and the end of each process is delayed. There is a problem of end. As the entire process for the power failure data is delayed, there is a problem that the minimum necessary processing of grasping and outputting the situation of when and where the power failure has occurred is stagnant. Furthermore, there is a risk that contact with a customer who is presumed to have a power outage will be delayed.

  The present invention has been made in view of the above problems, and its main purpose is to preferentially output the power outage status in the power outage information management system.

In order to solve the above-described problem, the present invention is a power failure information management system, and stores a section / address correspondence information in which a section number of a power distribution system is associated with an address code unique to an address of the section. An address correspondence information storage unit, a map information storage unit that stores map information that can identify an area corresponding to the address code, and a customer information storage unit that stores customer information including a customer name and the address code of the customer; A power pole / address correspondence information storage unit for storing a power pole / address correspondence information in which a power pole number of the power distribution system is associated with an address code unique to the address of the power pole, and a power distribution system relating to a section of the power distribution system and a configuration of the power pole a distribution system information storing unit for storing information, indicates that the power failure in the power distribution system has occurred, and a communication unit for receiving a plurality of power failure data including the section number a power failure occurs, the communication unit is the blackout data When received, the map information corresponding to the address code is identified with priority by referring to the section / address correspondence information, specifying the address code associated with the section number included in the received power failure data Generate and output map display data for displaying the upper area in a manner distinguishable from areas other than the area, refer to the customer information, and identify the customer name of the power failure target from the identified address code And a processing unit that outputs an emergency contact file including the name of the customer subject to power outage and the address code of the customer, and the processing unit is specific to the power outage data corresponding to each received power outage data. Power outage transaction information including the power outage number, section number, power outage type code, and utility pole number, and storing the outage transaction information. Stores in the information storage unit, by referring to the telephone pole and address correspondence information to identify the address code associated with said electric pole number of the power failure transaction information, by referring to the customer information, the address code The customer name is identified from, and customer history information including the power outage number of the power outage transaction information is created for each customer name, and the distribution system information is referred to, and a plurality of data related to the configuration of the section If there is inconsistency, refer to the section / address correspondence information, identify the address code from the section number, refer to the distribution system information, and mismatch between a plurality of data related to the configuration of the utility pole The address code is identified from the utility pole number, the address code is identified from the customer pole information, and the identified residence is identified. The customer name is identified from the location code, and inconsistent customer information including the customer name, telephone pole number, and address code is created .
According to this configuration, even when a large number of communication data (packets) generated at the time of a power failure is received, the highest priority and minimum information indicating when and where the power failure has occurred can be output. According to this, the minimum necessary processing can be performed first without congesting a plurality of processes in the system.
And since the emergency contact file which consists of the customer name and address code of a power failure target can be acquired, first, the customer subject to a power failure can be promptly contacted.
Further, once the power failure transaction information corresponding to the received power failure data is stored, the contents can be secured. According to this, even when a large number of communication data (packets) generated at the time of a power failure is received, priority is given to urgent processing such as display of map information and output of an emergency contact file, Internally closed processing can be performed without congestion.
In addition, by creating a history of accident power outages for each customer, it is possible to respond to each customer in preparation for a power outage that may occur in the future.
And when there is inconsistency in the distribution system information related to the section and power pole configuration, it creates information about the customers receiving power distribution from that section and power pole, and promotes the elimination of the inconsistency in the distribution system information. It can be considered that there is a possibility of inconvenience such as a power failure until it is resolved.

  The present invention also includes a power failure information management method. In addition, the problems disclosed in the present application and the solutions thereof will be clarified by the column of the best mode for carrying out the invention and the drawings.

  According to the present invention, in the power failure information management system, it is possible to preferentially output the power failure status.

  Hereinafter, the best mode for carrying out the present invention will be described with reference to the drawings. The power outage information management system according to the embodiment of the present invention receives power outage data from the distribution automation system, updates and manages information about the power outage based on the power outage data, and manages the information about the outage as needed. It is to provide. In updating and managing the information, information of each DB (Data Base) reflecting information of the distribution automation system, the distribution system, and the sales system is referred to.

≪System configuration and overview≫
FIG. 1 is a diagram illustrating a configuration of a power distribution management system 1 according to the present embodiment. The distribution management system 1 is a system that manages and manages the power distribution system in order to smoothly distribute power from the power company's substation to the customer. The power failure information management system 2, the distribution automation system 3, the power distribution system 4, and the sales system 5 It is a configuration that includes. The power failure information management system 2 and the distribution automation system 3 are each realized by a server computer, and these systems can communicate with each other via a LAN (Local Area Network). The power distribution system 4 and the sales system 5 are realized by a host computer (large general-purpose computer), but may be in the same computer or may be divided into different computers. These systems can communicate with each other via an interface between host processing modules or an interface between hosts. Further, the power failure information management system 2 and the power distribution automation system 3, and the power distribution system 4 and the sales system 5 can communicate with each other via a server-host interface (to-host communication interface).

  The power failure information management system 2 receives the power failure data transmitted from the power distribution automation system 3 along with the event related to the power failure, and updates various DBs related to the power failure based on the power failure data. At that time, a DB (substation DB or the like) reflecting information of the power distribution system 4 and the sales system 5 is referred to. In addition, in response to a request from a customer, information regarding power outages in various DBs is provided.

  The distribution automation system 3 constantly monitors the distribution system, grasps the occurrence and recovery status of the power outage, updates its own DB with the power outage data in accordance with the status, and manages the power outage data in the power outage information management. Send to system 2. In addition, the information in the DB related to substations, feeders and section configurations (section numbers and column numbers) managed by each business office is updated as needed in response to power outages and other changes in the distribution system. Information is immediately transmitted to the power failure information management system 2. At this time, the power failure information management system 2 reflects the update information received from the distribution automation system 3 in its own DB (substation DB, feeder DB, and section DB). Thereby, the immediate cooperation of the information regarding the substation of each sales office, a feeder, and section structure is implement | achieved between the distribution automation system 3 and the power failure information management system 2. FIG.

  Power distribution system 4 manages and designs information in DB related to high voltage system (component column number and transformer column number), load (transformer column number and drop column number) and pull column (draw column number and contract number) The information on the high voltage system etc. is updated from time to time according to the information on the equipment installation etc. input by the person in charge (operator), and the updated information is updated to the power outage information management system 2 once a day (for example, at night). Send. At this time, the power failure information management system 2 reflects the update information received from the power distribution system 4 in its own DB (section DB, transformer column DB, and service column DB). Thereby, the daily cooperation of the information regarding a high voltage | pressure system, a load, and a drawing column is implement | achieved between the power distribution system 4 and the power failure information management system 2. FIG.

  The sales system 5 manages information related to the service pillars (service service pillars and contract numbers), calculates the power charges of each customer, and manages information related to the customers (contract number, address, TEL, etc.). When the service pole or power charge is updated, its own DB is updated with the updated information, and the update information is transmitted to the power failure information management system 2 once a day (in the daytime or at night). At this time, the power failure information management system 2 reflects the update information received from the sales system 5 in its own DB (section DB, transformer column DB, and service column DB). Thereby, the daily cooperation of the information about the service pillar and the customer is realized between the sales system 5 and the power failure information management system 2. In addition, the power distribution system 4 and the sales system 5 are coordinated on a daily basis (nighttime) with respect to information about the service pole.

  FIG. 2 is a diagram illustrating a configuration of the power failure information management system. The power failure information management system 2 includes a communication unit 21, a display unit 22, an input unit 23, a processing unit 24, and a storage unit 25. The communication unit 21 is a part that enables communication with the distribution automation system 3, the distribution system 4, and the sales system 5 and performs data transmission / reception, and is realized by a NIC (Network Interface Card) or a transmission / reception circuit. The display unit 22 is a part that displays predetermined data in accordance with an instruction from the processing unit 24, and is realized by a liquid crystal display (LCD) or the like. The input unit 23 is a part in which an operator inputs predetermined data, and the data acquired by the input is transferred to the processing unit 24, and is realized by a pointing device such as a keyboard or a mouse. The processing unit 24 controls the entire power failure information management system 2 and updates and manages each DB according to the power failure data received from the power distribution automation system 3, and is stored in a predetermined memory by a CPU (Central Processing Unit). This is realized by executing the programmed program. The storage unit 25 is a part that stores data (including DB records) from the processing unit 24 and reads the stored data, and is realized by a nonvolatile storage device such as a flash memory or a hard disk device.

  As with the power failure information management system 2, the power distribution automation system 3, the power distribution system 4, and the sales system 5 also include a communication unit, a display unit, an input unit, a processing unit, and a storage unit. Each system (the power failure information management system 2, the distribution automation system 3, the distribution system 4 and the sales system 5) is not limited to one computer, and may be configured by connecting two or more computers.

<< Data structure >>
FIG. 3 is a diagram illustrating a configuration of the DB stored in the storage unit 25 of the power failure information management system 2. First, in the storage unit 25, as a power failure-related information DB for generating or updating a record upon reception of power failure data, a map DB 251, power failure status DB 252, power failure management DB 253, power failure transaction DB 254, power failure management details DB 255, customer history DB 256 are stored. Inconsistent customer DB 257, emergency contact file 258, and disaster information file 259 are stored.

  The map DB 251 stores map data that covers areas covered by the power distribution management system 1 and is used for coloring and displaying power outage areas. The power failure situation DB 252 stores an external situation of a power failure. When the power failure management DB 253 receives power failure data whose power failure type is “determined”, the power failure management DB 253 stores a record of management information related to the power failure indicated by the power failure data and recovery thereof. The power failure transaction DB 254 stores a record corresponding to the power failure data received by the power failure information management system 2. The power failure management detail DB 255 stores detailed information of the power failure target section. The customer history DB 256 creates a power outage history for each customer and stores a record of the power outage history. The inconsistent customer DB 257 extracts a customer who receives power distribution from the section or the power pole when there is a mismatch in the information about the section or the power pole in the power distribution system, and stores the information about the customer. The emergency contact file 258 stores information (address name, customer name, etc.) related to a customer receiving power distribution from a power distribution system within the range of the power failure when the power failure data is received. The disaster information file 259 stores disaster information that summarizes the damage caused by the power outage from the record in the power outage management DB 253.

  Next, the storage unit 25 stores a section / address correspondence DB 260 and a utility pole / address correspondence DB 261 as intermediate information DBs for generating a record relating to the distribution system. The section / address correspondence DB 260 is a DB that associates a section number of the power distribution system with an address code unique to the address of the section. According to this, when the section number of the power outage is known, the address code of the section can be specified from the section number, and the inhabitant of the address can be specified from the address code, so the emergency contact file 258 is created. be able to. The utility pole / address correspondence DB 261 is a DB for associating the utility pole number of the transformer pole or the service pole with the address code unique to the address of the utility pole. According to this, when the power pole number of the power outage is known, the address code of the power pole can be specified from the power pole number, and further, the resident of the address can be specified from the address code, so the customer history DB 256 is created. Can do.

  The storage unit 25 includes a substation DB 262, a feeder DB 263, a section DB 264, a transformer column DB 265, as a distribution system and customer related information DB reflecting the information of the distribution automation system 3, the distribution system 4 and the sales system 5. A service pole DB 266, a track name DB 267, a customer search basic information DB 268, a temporary registration DB 269, a power failure customer information DB 270, and a contact customer information DB 271 are stored.

  The substation DB 262 stores a sales office and a substation in association with each other. The feeder DB 263 stores a substation and a feeder in association with each other. The section DB 264 stores a feeder, a distribution automation section, and a high-voltage system section in association with each other. The transformer column DB 265 stores the number of each section of the distribution system and the number of the transformer column in association with each other. The drawing column DB 266 stores the number of the transformer column and the number of the drawing column in association with each other. The track name DB 267 stores a symbol-to-Japanese conversion table related to sections of the distribution system, utility poles, customers, and the like. The customer search basic information DB 268 stores a drawing column number and a contract number in association with each other. When registering a new customer, the temporary registration DB 269 has a premise that data linkage is not performed until the processing being executed first is completed. At that time, the sales representative performs temporary registration using the temporary number, Information regarding the temporary registration is stored. The power failure customer information DB 270 stores information for identifying a customer estimated to have a power outage. The contact customer information DB 271 stores the contact information of the customer estimated to have a power outage.

  The storage unit 25 further stores a customer information DB (not shown) that stores an address code, a customer name corresponding to the address of the address code, and a contact address (such as a telephone number) in association with each other. Shall be.

  4 to 7 are diagrams showing the structures of data, DBs, and files handled by the power failure information management system 2.

FIG. 4A shows the configuration of the power failure data 250. The power failure data 250 is packet data that the power failure information management system 2 receives from the power distribution automation system 3 when an accidental power failure occurs or a construction power failure occurs. The power failure data 250 includes a power failure type code 2501, a section number 2502 and a date and time 2503. The power failure type code 2501 indicates the type of event related to a power failure. The power failure type code 2501 related to the accident power failure includes “occurrence”, “confirmation”, “self-recovery end”, and “section recovery”. “Generation” indicates that a power outage has occurred even for a moment (short time). “Confirmed” indicates that the power outage state has continued for a predetermined time or more, so it is determined that the power outage state has been confirmed. “End of self-recovery” indicates that the power supply is automatically restored by the autonomous operation of the power distribution management system 1. “Section restoration” indicates that power is restored in the human system for each section of the distribution system. On the other hand, the power failure type code 2501 relating to the work power failure includes “construction start” and “construction end”. “Construction start” indicates that a power outage starts with the start of the construction. “End of construction” indicates that the power outage is over with the completion of construction.
The section number 2502 is a number assigned to each section of the power distribution system. Date and time 2503 indicates the date and time when the event related to the power failure occurred.

Each DB is stored in the storage unit 25 of the power failure information management system 2.
FIG. 4B is a diagram illustrating the configuration of the map DB 251. The map DB 251 includes records including a business office code 2511, map data 2512, address code 2513, area range 2514, coloring 2515, number of accident blackouts 2516 and number of construction blackouts 2517. The sales office code 2511 is a code unique to one sales office in the area managed by the power failure information management system 2. The map data 2512 covers the area corresponding to the sales office of the sales office code 2511. For example, the map data 2512 is data necessary for displaying a map of the area on the display unit 22. The address code 2513 is a code unique to each address in the area corresponding to the sales office, and the area range 2514 or the number of construction blackouts 2517 is set for each address code 2513. The area range 2514 is an area range on the map data 2512 indicated by the address code 2513. For example, the area range 2514 may be a rectangular area by specifying the x-coordinate range and the y-coordinate range, but is not necessarily limited to the rectangular area. is not. The coloring 2515 is a color that fills the area range 2514 on the map data 2512 in order to clarify the occurrence of a power failure. If there is no power failure at the address of the address code 2513, the coloring 2515 is invalid. The number of accidental power outages 2516 is the number of accidental power outages occurring at the address. The number of construction blackouts 2517 is the number of construction blackouts occurring at the address.

  FIG. 4C is a diagram illustrating a configuration of the power failure situation DB 252. The power outage status DB 252 includes records including a business office code 2521, an address code 2522, a power outage number 2523, a power outage classification 2524, a number of power outages 2525, an accident occurrence date 2526, a complete recovery date 2527, a construction start date 2528, and a construction end date 2529. . The power failure number 2523 is a number unique to the power failure data 250 received by the power failure information management system 2. The power outage section 2524 indicates whether the power outage is an accident power outage or a construction power outage. When the power failure classification 2524 is an accident power failure, the accident occurrence date and time 2526 and the complete recovery date and time 2527 are valid. On the other hand, when the power failure classification 2524 is a construction power failure, the construction start date and time 2528 and the construction end date and time 2529 are valid.

  FIG. 5A is a diagram illustrating a configuration of the power failure management DB 253. The power outage management DB 253 includes an office code 2531, a power outage number 2532, a power outage start date and time 2533, a power outage end date and time 2534, a substation code 2535, a feeder code 2536, a power outage category 2537, a power outage unit 2538, a number of restored units 2539, an accident confirmation date and time 253A, The record includes a recovery date / time 253B, a construction start date / time 253C, and a construction end date / time 253D. When the power failure classification 2537 is an accident power failure, the accident confirmed date 253A and the scheduled recovery date 253B are valid. On the other hand, when the power failure classification 2537 is a construction power failure, the scheduled construction start date and time 253C and the planned construction end date and time 253D are valid.

  FIG. 5B shows the configuration of the power failure transaction DB 254. The power failure transaction DB 254 includes records including a power failure number 2541, an automated section number 2542, a power failure type code 2543, a power failure range code 2544, a power pole number 2545, a power failure start date and time 2546, a power failure end date and time 2547, and a construction plan number 2548. The power failure number 2541 is a number unique to the power failure data 250 received by the power failure information management system 2. The automation section number 2542 indicates the number of the section when power supply is automatically restored. The power failure type code 2543 is the same as the power failure type code 2501 included in the power failure data 250. The power outage range code 2544 is a code indicating a section of the power outage range, and the code includes “section”, “transformer column”, and “lead column”. The utility pole number 2545 indicates the number of a utility pole when an event relating to a power failure relates to a particular utility pole (transformer pole or service pole). The power outage start date and time 2546 is literally the time when the power outage started, but in the case of an accident power outage, it is the date and time when the power outage occurred even for a moment (short time), and in the case of a construction power outage, the date and time when construction was started . The power outage end time 2547 is literally the time when the power outage ended, but in the case of an accident power outage, it is the date when the power supply in all sections was restored, and in the case of a construction power outage, the date when construction was completed. The construction plan number 2548 is the number of the construction plan in the case of a construction power outage.

  FIG. 6A is a diagram illustrating a configuration of the power failure management details DB 255. Power failure management details DB 255 includes power failure management detail number 2551, sales office code 2552, power failure number 2553, substation code 2554, feeder code 2555, transformer pole number 2556, service pole number 2557, address code 2558, power failure occurrence date and time 2559, It consists of a record including a power failure recovery date and time 255A, a power failure home number 255B, and a recovery home number 255C. The power failure management detail number 2551 is a number unique to each record in the power failure management detail DB 255. The transformer pillar number 2556 and the lead-in pillar number 2557 indicate the numbers of the transformer pillar and the lead-in pillar in the power failure target section.

  FIG. 6B is a diagram showing the configuration of the customer history DB 256. The customer history DB 256 includes a record including a contract number 2561, a customer name 2562, and a power outage number 2563. The number of power outages 2563 is not necessarily one, but the number of power outages 2563 corresponding to the number of times of power outages affected by the customer is stored.

  FIG. 6C is a diagram showing the configuration of the inconsistent customer DB 257. The inconsistent customer DB 257 is composed of records including a drawing column number 2571, an address code 2572, a section number 2573, and a contract number 2574. The service post number 2571 indicates the number of the service post that distributes power to the customer. The address code 2572 indicates the address code of the customer's home. The section number 2573 is a section of an urban area in the address, and indicates a “chome” number indicating a small section in the town. The contract number 2574 is a contract number between the customer and the electric power company. Note that the record of the inconsistent customer DB 257 may further include a customer name.

  FIG. 6D is a diagram illustrating a configuration of the section / address correspondence DB 260. The section / address correspondence DB 260 is a DB that associates a section with an address, and includes a record including a section number 2601 and an address code 2602. The section number 2601 is a number assigned to each section of the distribution system. The address code 2602 is an address code that covers customers who receive power from the section indicated by the section number 2601. The section / address correspondence DB 260 is created from the section DB 264, the transformer column DB 265, and the lead-in column DB 266 at night.

  FIG. 7A is a diagram showing the configuration of the emergency contact file 258. Power outage number 2581, service pole number 2582, contract number 2583, address name 2584, customer name 2585, place of use telephone number 2586, contract type 2587, contract power 2588, instrument number 2589, engineer name 258A and engineer phone number It consists of records including 258B.

  FIG. 7B is a diagram showing the configuration of the disaster information file 259. The disaster information file 259 includes an office code 2591, a substation code 2592, a feeder code 2593, an accident name 2594, an address code 2595, a power outage date and time 2596, a restoration date and time 2597, a substation name 2598, a feeder name 2599, an address name 259A, an accident It consists of a record including the content 259B, the current number of power outage units 259C, the total number of distributed customer units 259D and the number of power outage sections 259E. The number of current power outages 259C is the current number of power outages per unit of accident 2594 managed by the power distribution automation system 3 in the business office with the business office code 2591. The total number of customers per customer 259D is the total number of customers managed by the distribution automation system 3 in the business office with the business office code 2591.

  4 to 7 show examples of data, DB, and file configurations handled by the power failure information management system 2, and other configurations may be used. For example, a part of the item data may be changed or deleted, or other item data may be further included.

≪System processing≫
FIG. 8 is a flowchart showing the processing of the power failure information management system 2. Here, the case of an accidental power outage will be described in particular, but the processing content is also applicable to the case of a construction power outage.

  First, the power failure information management system 2 receives the power failure data 250 from the power distribution automation system 3 via the LAN (S801). In this case, a record corresponding to the received power failure data 250 is stored in the power failure transaction DB 254 of the storage unit 25. Among the records to be stored, items to be determined at this time include at least a power failure number 2541 and a power failure type code 2543. The power failure number 2541 is a serial number given to the power failure data 250. In the power failure type code 2543, a power failure type code 2501 included in the power failure data 250 is set. Other items are determined and set sequentially in accordance with the process related to the power failure and recovery.

  Next, the power failure information management system 2 colors the power failure range in the map data 2512 stored in the map DB 251 (S802). Specifically, the section number 2502 is extracted from the received power failure data 250, and the address code corresponding to the extracted section number is specified with reference to the section / address correspondence DB 260. Then, the area range 2514 corresponding to the identified address code 2513 in the map data 2512 is painted in a color indicating the power failure range. In this case, the map data 2512 itself may be colored, or the color 2515 may be set and the corresponding range may be colored when displaying the map. Regardless of the method of coloring and displaying the map, the data necessary for displaying such a map is referred to as map display data. In the power outage information management system 2, the processing unit 24 may display map data colored in the power outage range on the display unit 22 or transmit it to other terminals via the communication unit 21 in response to a request. it can.

  FIG. 9 is a diagram illustrating an example of a power outage section display screen in which the power outage range is colored. Of the rectangular area set for each section number “Chome”, A West 3 Chome, A East 4 Chome, B West 2 Chome, and B East 1 Chome are colored as power outages.

  Subsequently, the power failure information management system 2 confirms that the power failure type code 2501 has received the “failed” power failure data 250, and then writes management information related to the power failure and recovery to the power failure management DB 253 (S803).

  Then, the power failure information management system 2 outputs an emergency contact customer list (S804). This is because by listing the contact information such as the telephone number of the customer (customer) that is estimated to have a power outage, the operator who received it will immediately contact the customer with the power outage. This is to convey notes etc. Specifically, first, the customer name and contact information (telephone number, etc.) corresponding to the address code specified in S802 are extracted from the customer information DB (not shown) of the sales system 5, and the address name 2584, the customer name are extracted. 2585 and the use place telephone number 2586 are stored in the storage unit 25 as the emergency contact file 258. Next, an address name, a customer name, and a place-of-use telephone number are read out from the storage unit 25 and displayed as a list on the display screen as an emergency contact customer list or printed on a printer. Furthermore, an automatic telephone call may be made, or an e-mail may be sent if there is a mail address.

  Furthermore, the power failure information management system 2 updates the target section information regarding the section where the self-recovery has been completed or the section has been restored (S805). Specifically, the power failure management details DB 255 is referred to and updated.

  Further, the power failure information management system 2 creates an individual power failure history regarding the section where the self-recovery has been completed or the section has been restored (S806). Specifically, the address code is specified from the utility pole number 2545 included in the record of the power failure transaction DB 254 with reference to the utility pole / address correspondence DB 261. Next, referring to the customer information DB, the customer name is specified from the address code. Then, a record including the power failure number 2563 (power failure number 2541 included in the record of the power failure transaction DB 254) is created or updated for each customer name 2562, and stored in the customer history DB 256 in the storage unit 25. A contract number 2561 corresponding to the customer name 2562 is set at the top of the record of the customer history DB 256.

  Subsequently, the power failure information management system 2 extracts inconsistent customers (S807). Specifically, first, the section DB 264, the transformer pole DB 265, the pull-in pole DB 266, and the customer search basic information DB 268 are referred to, and it is confirmed whether or not there is inconsistency in the information in the DB or information between the DBs. If there is an inconsistency in the section configuration, the address code is specified from the section number with reference to the section / address correspondence DB 260. When there is a mismatch in the configuration of the utility pole, the address code is identified from the utility pole number with reference to the utility pole / address correspondence DB 261. Next, referring to the customer information DB, the corresponding customer name is extracted from the identified address code. And the record regarding the extracted customer is stored in inconsistent customer DB257.

  The inconsistencies are the distribution automation section and the high-voltage system section in the section DB 264, the high-voltage system section and the section of the transformer column DB 265 of the section DB 264, the transformer column of the transformer column DB 265 and the transformer column of the pull-in column DB 266, and the pull-in column DB 266. May occur between each of the service columns and the service search basic information DB 268. For example, in the section DB 264, the distribution automation section is specified by the section number and the section configuration column number, and the high voltage system section is specified by the section configuration column number, so even if the section configuration column numbers at both ends match, It is possible that the distribution automation section and the high-voltage system section become inconsistent because the state does not match.

  Although the embodiment of the present invention has been described above, in order to make each unit in the power failure information management system 2 shown in FIG. 2 function, a program executed by the processing unit 24 is recorded on a computer-readable recording medium, It is assumed that the power failure information management system 2 according to the embodiment of the present invention is realized by causing the computer to read and execute the recorded program. Note that the program may be provided to the computer via a network such as the Internet, or a semiconductor chip or the like in which the program is written may be incorporated in the computer. The above contents can also be applied to the distribution automation system 3, the distribution system 4, and the sales system 5.

  Although the best mode for carrying out the present invention has been described above, the above embodiment is intended to facilitate understanding of the present invention and is not intended to limit the present invention. The present invention can be changed and improved without departing from the gist thereof, and equivalents thereof are also included in the present invention.

It is a figure which shows the structure of a power distribution control system. It is a figure which shows the structure of a power failure information management system. It is a figure which shows the structure of DB stored in the memory | storage part of a power failure information management system. It is a figure which shows the structure of data and DB which a power failure information management system handles, (a) shows the structure of power failure data 250, (b) shows the structure of map DB251, (c) shows the structure of power failure situation DB252. Show. It is a figure which shows the structure of DB which a power failure information management system handles, (a) shows the structure of power failure management DB253, (b) shows the structure of power failure transaction DB254. It is a figure which shows the structure of DB which a power failure information management system handles, (a) shows the structure of power failure management detail DB255, (b) shows the structure of customer history DB256, (c) shows the structure of inconsistent customer DB257. (D) shows the configuration of the section / address correspondence DB 260. It is a figure which shows the structure of the file which a power failure information management system handles, (a) shows the structure of the emergency contact file 258, (b) shows the structure of the disaster information file 259. It is a flowchart which shows the process of a power failure information management system. It is a figure which shows the example of a power failure area display screen.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Power distribution control system 2 Power failure information management system 21 Communication part 22 Display part 23 Input part 24 Processing part 25 Storage part 251 Map DB (map information)
254 Power failure transaction DB (power failure transaction information)
256 Customer history DB (customer history information)
257 Inconsistent customer DB (Inconsistent customer information)
258 Emergency communication file 260 Section / address correspondence DB (section / address correspondence information)
261 Telephone pole / address correspondence DB (Pole / address correspondence information)
H.264 section DB (distribution system information)
265 Transformer column DB (distribution system information)
266 service column DB (distribution system information)
268 Customer Search Basic Information DB (Distribution System Information)
3 Power distribution automation system 4 Power distribution system 5 Sales system

Claims (2)

A section / address correspondence information storage unit for storing section / address correspondence information in which a section number of the distribution system is associated with an address code unique to the address of the section;
A map information storage unit for storing map information capable of specifying an area corresponding to the address code;
A customer information storage unit for storing customer information including the customer name and the address code of the customer;
A utility pole / address correspondence information storage unit for storing utility pole / address correspondence information in which a utility pole number of a distribution system is associated with an address code unique to the address of the utility pole;
A power distribution system information storage unit for storing power distribution system information related to the section of the power distribution system and the configuration of the power pole;
A communication unit that indicates that a power outage has occurred in the power distribution system and receives a plurality of power outage data including the section number where the power outage occurred,
When the communication unit receives each power outage data, preferentially refer to the section / address correspondence information, identify the address code associated with the section number included in the received power outage data, and Generate and output map display data for displaying an area on the map information corresponding to the address code in a manner distinguishable from areas other than the area, and refer to the customer information to identify the address code identified. A processing unit for identifying the customer name subject to power outage and outputting an emergency contact file including the customer name subject to power failure and the address code of the customer;
With
The processor is
Corresponding to each received power outage data, create a power outage transaction information including a power outage number, section number, power outage type code and power pole number specific to the power outage data, and store the power outage transaction information in the power outage transaction information storage unit stores,
Referring to the utility pole / address correspondence information, identify the address code associated with the utility pole number of the blackout transaction information, refer to the customer information, identify the customer name from the address code, Create customer history information including the power outage number of the power outage transaction information for each customer name,
When there is a mismatch between a plurality of data related to the configuration of the section with reference to the power distribution system information, the address code is identified from the section number with reference to the section / address correspondence information, and the power distribution When there is a mismatch between a plurality of data related to the configuration of the utility pole with reference to grid information, the address code is identified from the utility pole number with reference to the utility pole / address correspondence information, and the customer information is A power failure information management system characterized in that the customer name is identified from the identified address code, and inconsistent customer information including the customer name, telephone pole number, and address code is created . A power failure information management method for managing power failure information by a computer including a processing unit and a storage unit,
The processor is
Storing the section / address correspondence information in which the section number of the distribution system is associated with the address code unique to the address of the section in the storage unit;
Storing map information capable of specifying an area corresponding to the address code in the storage unit;
Storing customer information including a customer name and the address code of the customer in the storage unit;
A step of indicating that a power failure has occurred in the power distribution system, and receiving a plurality of power failure data including a section number where the power failure has occurred;
When receiving each blackout data, prioritize the section / address correspondence information, identify the address code associated with the section number included in the received blackout data, and correspond to the address code Generating and outputting map display data for displaying the area on the map information in a manner distinguishable from areas other than the area; and
Referring to the customer information and identifying the customer name subject to the power outage from the identified address code;
Outputting to the output unit an emergency contact file comprising the name of the customer subject to a power failure and the address code of the customer;
Corresponding to each received power outage data, creating a power outage transaction information including a power outage number specific to the power outage data, a section number, a power outage type code and a power pole number, and storing in the storage unit;
Storing power pole / address correspondence information in which the power pole number of the power distribution system and the address code unique to the address of the power pole are associated with each other in the storage unit;
Identifying the address code associated with the utility pole number of the power outage transaction information with reference to the utility pole / address correspondence information;
Identifying the customer name from the address code with reference to the customer information;
Creating customer history information including the power outage number of the power outage transaction information for each customer name;
Storing power distribution system information regarding the section of the power distribution system and the configuration of the power pole in the storage unit;
With reference to the power distribution system information, when there is a mismatch between a plurality of data related to the configuration of the section, referring to the section / address correspondence information, identifying the address code from the section number;
With reference to the power distribution system information, when there is a mismatch between a plurality of data related to the configuration of the utility pole, referring to the utility pole / address correspondence information, identifying the address code from the utility pole number;
Referring to the customer information, identifying the customer name from the identified address code, creating inconsistent customer information including the customer name, telephone pole number and address code;
The power failure information management method characterized by performing.