JP4850171B2 - Power failure information integration system and power failure information integration method - Google Patents

Description

  The present invention relates to a power failure information integration system that aggregates, manages, and can be referred to from other systems regarding information regarding power failures for each sales office.

Since the power outage information management system is a distributed system built on a distribution server that is closed in the sales office of an electric power company, it has traditionally been possible to grasp the power outage status at each office in the company using the system. I could not. Therefore, for accidental power outages, priority is given to customers in each jurisdiction within the jurisdiction and on-site awareness, so the situation regarding power outages within the jurisdiction and recovery will be delayed to other business offices by telephone, fax, e-mail, etc. I was informed. On the other hand, regarding construction blackouts, there was no notification to other sales offices of the schedule of constructions to be carried out by the sales offices, the areas where power outages occur, and the names of customers subject to power outages. Note that Patent Document 1 discloses a system that transmits information such as the occurrence date of a power outage and the recovery expectation to consumers in the area where the power outage occurred.
JP 2006-191281 A

  As described above, conventionally, even in the case of an accidental power outage due to a large-scale disaster, the business office has not provided real-time power outage information to other business offices. In addition, because the power outage information is not shared between the sales offices, the number of customers who receive a post response (contact after confirming the cause of power outage and recovery status) has increased, and the response has been delayed.

  The present invention has been made in view of the above-mentioned problems, and its main purpose is to share power outage information so that it can be referred to at any time.

In order to solve the above problems, the present invention is a power failure information integration system , comprising a storage unit and a processing unit, wherein the processing unit is provided corresponding to each sales office of an electric power company, and the corresponding sales office The first power outage information related to the occurrence of a power outage including the area map information in the jurisdiction of the sales office and the position information of the power outage occurrence section in the area map information is received from the power outage information management system storing the power outage information in the jurisdiction of when, and means for storing the first power failure information received in the storage unit for each unique office code to the sales office, prior Symbol first power outage of each office code stored in the storage unit It means for transmitting information before Symbol first power failure information power failure information management system other than the power failure information management system which is the transmission source of the power failure information management system which is the transmission source of the first power failure information, the power failure section Contains information about the update information and the power is restored, when receiving the second power failure information about the state change after a power failure, Update in the storage unit the second power failure information received for each of the office code means for storing, when the power failure information management system receives a request for acquisition of the second power failure information, those the power failure information managing the latest of the second power failure information for each office code stored in the storage unit Means for transmitting to the system .

According to this configuration, the power failure information for each business office is consolidated from the system of each business office into the power failure information integrated system, and the first power failure information related to the occurrence of the power failure is unconditionally the first power failure information. Send to a system other than the sender of According to this, it is possible to notify the important information about the occurrence of a power failure to each sales office and customer center of the electric power company, and those who have received a notification of the occurrence of a power failure can respond quickly. Moreover, the 2nd power failure information regarding the state change after a power failure occurs among power failure information is provided when there is an acquisition request. According to this, there are some other sales offices that do not need to respond in particular because the power distribution system is different from that of the power outage occurrence location. By transmitting the power outage information of 2, it is possible to provide information efficiently without waste.
And since the map information showing the power outage section can be obtained and referenced when a power outage occurs, not only at the business office that detected the power outage within the jurisdiction but also at each other business office, Consider impacts and take prompt action.
In addition, since it is possible to acquire and refer to the increase / decrease and restoration status of the power outage section after the occurrence of a power outage, each business office can take appropriate measures while grasping the situation as necessary.

Moreover, this invention is a power failure information integrated system, Comprising: When the said process part updates and memorize | stores the said 2nd power failure information in the said memory | storage part for every said sales office code , it is said 2nd power failure information. the update date and IP address of the power failure information management system which is the transmission source of the second power failure information, characterized in that it further stores in the storage unit for each of the office code.

  According to this configuration, since it is possible to specify the last update date and time and the last updater of the second power failure information related to the state change after the occurrence of a power failure, there is an effect of suppressing unauthorized information update.

  The present invention includes a power failure information integration 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, power failure information can be shared and referenced at any time.

  Hereinafter, the best mode for carrying out the present invention will be described with reference to the drawings. The power failure information integration system according to the embodiment of the present invention receives a power failure data in the jurisdiction of the sales office, updates and manages information related to the power failure based on the power failure data, Information related to the power failure is acquired, and is collected and stored in the Web server as information on the entire power company. And the information memorize | stored in Web server can be referred from another power failure information management system or a customer center system.

≪System configuration and overview≫
FIG. 1 is a diagram illustrating a configuration of a power distribution management system. The power 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 power distribution automation system 3, the power distribution system 4, the sales system 5, The power failure information integration system 6 and the customer center system 7 are included. 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). In particular, the power failure information management system 2 is realized by a distribution server of each business office. 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 integration system 6 is realized by a Web server, and the customer center system 7 is realized by a terminal computer such as a PC (Personal Computer) installed in a customer center in an electric power company. The power failure information integration system 6, the power failure information management system 2, and the customer center system 7 are, for example, an IP (Internet Protocol) address system via a public network using the Internet or a virtual private network (VPN). Can communicate with each other.

  The power failure information management system 2 receives the power failure data transmitted from the power distribution automation system 3 in response to the event related to the power failure as a distributed system at the sales office unit, and updates various DBs related to the power failure based on the power failure data. To do. 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. On the other hand, the power failure information management system 2 as a Web system provides information related to a power failure to the power failure information integration system 6, refers to information held by the power failure information integration system 6, and updates information provided by itself. To do. In realizing such Web functions, Java (registered trademark) intermediate codes (codes after compiling Java programs) are distributed to the servers of each power outage information management system 2, and the intermediate codes are mounted on each server. It is executed by a virtual machine (VM) specific to the operating system (OS).

  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.

  The power outage information integration system 6 receives and stores information on power outages within the jurisdiction of each business office from the power outage information management system 2 of each business office, and stores information on power outages in the power outage information management system 2 and the customer center system 7. provide.

  The customer center system 7 monitors the update status of the power outage information possessed by the power outage information integration system 6 for 24 hours. If the information is updated, the customer center system 7 immediately requests the power outage information integration system 6 to obtain the latest information. , Receive and store the latest information, and update the power outage related map information displayed on the screen to the latest state.

≪Configuration of power failure information management system≫
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, the sales system 5, and the power failure information integration system 6 and performs data transmission / reception, and is realized by a NIC (Network Interface Card) or a transmission / reception circuit. Is done. 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 of power failure information management system≫
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 for covering areas covered by a sales office and displaying colored areas of power outages. 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 (regional map information) 2512, an address code 2513, an area range 2514, a coloring 2515, an accident power outage unit 2516, and a construction power outage unit number 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, and is data necessary for displaying a map of the area on the display unit 22, for example. The address code 2513 is a code specific to each address in the area corresponding to the sales office, and the area range 2514 or the number of work power outages 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. It can also be said that the area range 2514 is position information of a power outage occurrence section. 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 a business 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 classification 2537, a power outage unit 2538, a restored unit number 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 outage management details DB 255 includes power outage management details number 2551, sales office code 2552, power outage number 2553, substation code 2554, feeder code 2555, transformer post number 2556, service post number 2557, address code 2558, power outage classification 2559, power outage It consists of a record including occurrence date / time 255A, power failure recovery date / time 255B, number of power failure units 255C, and number of recovery units 255D. The power failure management detail number 2551 is a number unique to each record in the power failure management detail DB 255. The power failure occurrence section can be specified by the substation code 2554, the feeder code 2555, the transformer column number 2556, and the lead-in column number 2557. 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 case 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.

≪Configuration of power failure information integration system≫
FIG. 8 is a diagram illustrating a configuration of the power failure information integration system. The power failure information integration system 6 includes a communication unit 61, a display unit 62, an input unit 63, a processing unit 64, and a storage unit 65. The communication unit 61 is a part that enables communication with the power failure information management system 2 and the customer center system 7 and performs data transmission / reception, and is realized by a NIC or a transmission / reception circuit. The display unit 62 is a part that displays predetermined data in accordance with an instruction from the processing unit 64, and is realized by a liquid crystal display or the like. The input unit 63 is a part for inputting predetermined data by an operator and transferring the data acquired by the input to the processing unit 64, and is realized by a pointing device such as a keyboard and a mouse. The processing unit 64 controls the entire power failure information integration system 6 and updates and manages each information according to the information about the power failure received from the power failure information management system 2. The CPU stores a program stored in a predetermined memory. It is realized by executing. The storage unit 65 is a part that stores data (including DB records) from the processing unit 64 and reads the stored data, and is realized by a nonvolatile storage device such as a flash memory or a hard disk device.

≪Data structure of power failure information integration system≫
FIG. 9 is a diagram illustrating the configuration of the DB stored in the storage unit 65 of the power failure information integration system 6. The storage unit 65 stores an overall map DB 651, a map DB 652, a power failure management details DB 653, and a provided information update DB 654. The overall map DB 651, the map DB 652, and the power failure management details DB 653 are DBs that store information on power failures that can be arbitrarily referred to from the power failure information management system 2 of each sales office of the power company and the customer center system 6 of the power company. The overall map DB 651 stores overall map information covering the entire area under the jurisdiction of the electric power company and location information of each sales office. The map DB 652 is map data that covers the areas that each business office has jurisdiction over, and is an aggregation of the map DB 251 stored in the storage unit 25 of each power outage information management system 2, and has the same data format as the map DB 251. Have The power outage management details DB 653 is detailed information on the sections subject to power outages in the area that each business office has jurisdiction, and is an aggregation of the power outage management details DB 255 stored in the storage unit 25 of each power outage information management system 2. It has the same data format as the power failure management details DB 255. The provided information update DB 654 stores information related to the update for each sales office when the information provided by the power failure information integration system 6 is updated by the power failure information management system 2 or the customer center system 7.

  FIG. 10 is a diagram showing the configuration of the provided information update DB 654. As shown in FIG. The provided information update DB 654 includes a record including an office code 6541, a last update date / time (storage date / time) 6542, and a last update node IP address (address) 6543. The sales office code 6541 is a code of a sales office related to the updated provision information. The last update date 6542 is the date when the provision information is finally updated. The last update node IP address 6543 is an IP address of a server, a PC, or the like that is a transmission destination of a provision information update request finally received by the communication unit 61 of the power failure information integration system 6. In addition to the final recording, a history within a predetermined period may be left. The provided information is information provided by the power outage information integration system 6 (map DB 652 and power outage management details DB 653). The original information is the map DB 251 received by the power outage information integration system 6 from the power outage information management system 2 and the power outage. This is an update content of the management details DB 255.

≪Processing of power failure information management system≫
FIG. 11 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 distribution automation system 3 via the LAN (S1101). 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 (S1102). 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. 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. 12 is a diagram illustrating an example of a power failure section display screen in which the power failure range is colored. Of the rectangular area set for each section number of “chome”, A west 3 chome, A east 4 chome, B west 2 chome and B east 1 chome are blackout sections, and are colored red, for example.

  Subsequently, the power failure information management system 2 confirms that the power failure data 250 whose power failure type code 2501 is “Confirmed” has been received, and then writes management information relating to the power failure and recovery thereof to the power failure management DB 253 (S1103).

  Then, the power failure information management system 2 outputs an emergency contact customer list (S1104). 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 precautions. Specifically, first, the customer name and contact information (telephone number, etc.) corresponding to the address code specified in S1102 are extracted from the customer information DB (not shown) of the sales system 5, and the address name 2584, 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-restoration has been completed or the section has been restored (S1105). Specifically, the power failure management details DB 255 is referred to and updated.

  In addition, the power failure information management system 2 creates an individual power failure history related to the section where the self-recovery has been completed or the section has been restored (S1106). 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 (S1107). 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 inconsistency includes the distribution automation section and the high-voltage system section in the section DB 264, the high-voltage system section and the transformer column DB 265 section, the transformer column DB 265 transformer column and the pull-in column DB 266 transformer column 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.

≪Processing of power failure information integration system≫
FIG. 13 is a flowchart showing the processing of the power failure information integration system 6. Here, the process of the power failure information management system 2 directly related to the process of the power failure information integration system 6 will be described.

  First, in the power failure information integration system 6, as an initial setting process, the processing unit 64 sets the entire map DB 651 in the storage unit 65 (S1301). Once this process has been performed, it is not necessary to perform this unless there is a change in the area of the electric power company's jurisdiction or the location of each sales office.

  When the power failure information management system 2 receives the power failure data from the distribution automation system 3, the power failure information management system 2 updates the map DB 251. At this time, the update content (first power failure information) is transmitted to the power failure information integration system 6 ( S1302). The update content includes, for example, map data 2512 for each sales office code 2511, an area range 2514 for each address code 2513, and the like. In the power failure information integration system 6, the communication unit 61 receives the update content, and the processing unit 64 stores the update content in the map DB 652 of the storage unit 65 (S1303). And the process part 64 acquires the whole map information (information of whole map DB651) and the newest map information (information of map DB652) of each sales office from the memory | storage part 65, and those information is blacked out via the communication part 61. It transmits to the other power failure information management system 2 which has not received data (S1304). Such information transmission to the other power failure information management system 2 is forcibly performed as an emergency contact to another business office when a power failure occurs. The other power failure information management system 2 receives the entire map information and map information from the power failure information integration system 6, stores them in the storage unit 25, and displays them on the display unit 22 (S1305).

  The power failure information display format includes a distribution chart and a list. FIG. 14 is a diagram illustrating an example in which power failure information is displayed as an accident power failure distribution map. The name of the dealer is displayed near the location of each sales office, the status, the number of power outages (approximate), and the presence / absence of notification are displayed in the frame below it, and the background color in the frame of “Notification” Indicated by. FIG. 15 is a diagram illustrating an example in which power failure information is displayed as an accident power failure list. Although not shown in FIG. 4 (b), the map DB 251 and the map DB 652 include the store name, state, number of power outages (estimated), presence / absence of notification, and disaster prevention system for each office code. The information is reflected in the power outage information display. The dealer name indicates the name and code of the sales office. The status indicates a power outage or recovery status. The number of power outages (estimated) indicates the estimated number of houses during a power outage. The presence / absence of notification indicates whether there is information to be notified to other sales offices. The disaster prevention system indicates the current disaster prevention system, and specifically includes a normal system, a warning system, an emergency system, and a special emergency system.

  Subsequently, when the power failure information management system 2 receives the power failure data from the power distribution automation system 3, the power failure management detail DB 255 is updated. At that time, the updated content (first power failure information) is updated to the power failure information integrated system. 6 (S1306). In the power failure information integration system 6, the communication unit 61 receives the update content, and the processing unit 64 stores the update content in the power failure management detail DB 653 of the storage unit 65 (S1307). Then, the processing unit 64 obtains the latest power outage management detailed information (information in the power outage management details DB 653) of each sales office from the storage unit 65, and receives the information about other power outage data not received via the communication unit 61. It transmits to the power failure information management system 2 (S1308). Such information transmission to the other power failure information management system 2 is forcibly performed as an emergency contact to another business office when a power failure occurs. The other power failure information management system 2 receives the power failure management detailed information from the power failure information integration system 6, stores it in the storage unit 25, and displays it on the display unit 22 according to the operation of the operator (S1309).

  For example, when a certain business office is clicked (selected) in the state where the accident power outage distribution map of FIG. 14 is displayed, a power outage section display screen as shown in FIG. 12 is displayed as a power outage occurrence state in the business office. The When a certain business office is clicked (selected) in the state where the accident power outage list of FIG. 15 is displayed, the distribution system information and the customer status information are displayed as the power outage occurrence status in the business office. The distribution system information indicates representative substations, feeders, transformer columns, and lead-in columns among the distribution systems in a power outage. This is complicated when displaying all the distribution system information during a power outage, so that the longest distribution system information of the distribution lines is displayed as a representative. The customer status information includes the customer's address, the number of houses in the address, the power outage or recovery status, the cause of the power outage, information on recovery, and an attached file. The attached file stores, for example, data other than text data such as on-site photo data, and the data in the attached file can be referred to by clicking the file name.

  In the case of an accidental power outage, customer status information can be updated from the Web screen. In that case, information about the update is stored. Details thereof will be described in S1312. In the case of a construction power outage, a customer list that is details of customer status information can be displayed. This is because the planned power outage range can be grasped in advance because it is a planned construction.

  Thereafter, when the power failure information management system 2 updates the map DB 251 and the power failure management details DB 255 by receiving data related to the state change after the occurrence of the power failure out of the series of power failure data, the update contents (second power failure) Information) is transmitted to the power failure information integration system 6 (S1310). The update contents include, for example, transformer pole number 2556, lead-in pole number 2557, power failure recovery date and time 255B, and the number of restored houses 255D. Note that the power outage information in the jurisdiction of the business office in the power outage information integration system 6 can be updated from the power outage information management system 2 or the customer center system 7 in the business office. In the power failure information integration system 6, the communication unit 61 receives the updated content, and the processing unit 64 stores the updated content in the map DB 652 and the power failure management detail DB 653 of the storage unit 65 (S1311). Then, the processing unit 64 updates the provided information update DB 654 in the storage unit 65 (S1312). Specifically, a last update date 6542 and a last update node IP address 6543 are set for each sales office code 6541. Note that the transmission of information regarding the state change after the occurrence of a power failure is not forcibly performed, but is performed in response to an inquiry (latest information acquisition request) from the power failure information management system 2 or the customer center system 7.

  Here, the server and the PC of the power failure information management system 2 are stored in the card every predetermined time period because the user cannot use the power failure information management system 2 without setting a personal card. The user IDs can be recorded sequentially. On the other hand, in the provision information update DB 654 of the storage unit 65 of the power failure information integration system 6, the last update date 6542 and the last update node IP address 6543 are set for each sales office code 6541. According to this, the server and PC of the power failure information management system 2 are specified from the last update node IP address 6542, and the user at the last update date and time 6541 is specified from the record of the server and PC, whereby the last update of the provided information is performed. Person can be identified. In addition, the name of the last updated person who has been identified is displayed on the display unit 22 of the server or PC of the power failure information management system 2 to notify that the user is recognized by the system. The deterrent effect which is not performed can be exhibited.

  The other power failure information management system 2 transmits a latest information acquisition request to the power failure information integration system 6 as necessary (S1313). This processing is performed, for example, when the “update information display” button is clicked in a state where the accident power failure distribution map of FIG. 14 or the accident power failure list of FIG. 15 is displayed. In the power failure information integration system 6, the communication unit 61 receives the latest information acquisition request from the other power failure information management system 2 (S1314). The processing unit 64 refers to the map DB 652 and the power failure management details DB 653 in the storage unit 65, and if there is further updated content from the previously transmitted update content, the updated content is converted into other power failure information as the latest information. It transmits to the management system 2 (S1315). The other power failure information management system 2 receives the latest information from the power failure information integration system 6, stores it in the storage unit 25, and displays it on the display unit 22 (S1316).

  Even when the customer center system 7 monitors the power outage status in each business office for 24 hours, the same processing as S1313 to S1316 is performed every predetermined time.

  Although the embodiment of the present invention has been described above, in order to make each unit in the power failure information integration system 6 shown in FIG. 8 function, a program executed by the processing unit 64 is recorded on a computer-readable recording medium, The power failure information integration system 6 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 power outage information management system 2, the power distribution automation system 3, the power distribution system 4, the sales system 5, and the customer center system 7.

  According to the embodiment of the present invention described above, by referring to the power outage information on the map displayed on the screen of the server or PC, within the jurisdiction of each business office according to the movement of lightning, typhoon, and rain. Since you can see at a glance how accidental power outages occur, preparations for power outages can be started early. Next, since the approximate number of power outages and the power outage status, such as momentary and long hours, can be easily understood with an address, the damage situation can be easily grasped.

  Also, if there is a PC terminal, anyone can inquire and update power outage information from anywhere, so even an inexperienced person can easily perform operations such as provision and inquiry of power outage information. According to this, the number of telephone correspondence with a customer increases markedly, and the contents can be enriched.

  In addition, regarding the construction blackout, the customer who is the target of the construction blackout can be identified and the well-known situation is linked. Therefore, even a customer other than the customer center or the well-known person can easily handle the customer. Furthermore, since the information update history remains, it has an effect of preventing malicious information from being falsified.

  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 figure which shows the structure of a power failure information integration system. It is a figure which shows the structure of DB stored in the memory | storage part of a power failure information integrated system. It is a figure which shows the structure of provision information update DB654 which a power failure information integration system handles. 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. It is a flowchart which shows the process of a power failure information integration system. It is a figure which shows the example which displayed the power failure information as an accident power failure distribution map. It is a figure which shows the example which displayed the power failure information as an accident power failure list.

Explanation of symbols

2 Power outage information management system (system other than system and sender)
251 Map DB
2511 Sales Office Code 2512 Map Data (Regional Map Information)
2514 area range (position information of power outage section)
6 Power failure information integration system 65 Storage unit 654 Provided information update DB
6541 Sales Code 6542 Last Update Date (Storage Date)
6543 IP address (address) of the last updated node
7 Customer Center System

Claims (4)

A storage unit and a processing unit;
The processor is
Power outage occurs in the regional map information within the jurisdiction of the sales office and the regional map information from the power outage information management system that is provided corresponding to each business office of the power company and stores the power outage information within the jurisdiction of the relevant business office including location information of the section, when receiving the first power failure information about a power failure, it means for storing in the storage unit for each unique office encoding said first power failure information received in the office,
It means for transmitting the pre-Symbol first power failure information for each office code stored in the storage unit before Symbol first power failure information power failure information management system other than the power failure information management system which is the source of the,
When the second power outage information related to the state change after the occurrence of the power outage is received from the power outage information management system that is the transmission source of the first power outage information, including the update information of the power outage occurrence section and the information about the power outage recovery , It means for storing the received second power failure information updates to the storage unit for each of the office code,
When the power failure information management system receives a request for acquisition of the second power failure information, means for transmitting the latest of the second power failure information for each office code stored in the storage unit to the person the power failure information management system When,
Power failure information integration system comprising: a. The power failure information integration system according to claim 1 ,
The processor is
Wherein when the second power failure information and stores the updated in the storage unit for each of the office code, the second power failure information update time and the second power failure information power failure information management system which is the transmission source of the power failure information integrated system characterized by the IP address further stored in the storage unit for each of the office code. A method of integrating power outage information by a computer system comprising a storage unit and a processing unit ,
From the power failure information management system in which the processing unit is provided corresponding to each business office of the electric power company and stores the power failure information within the jurisdiction of the corresponding business office , the regional map information and the region within the jurisdiction of the business office including location information of the power failure section in the map information, when receiving the first power failure information about a power failure, the storage unit for each unique office encoding said first power failure information received in the office Memorizing step ;
The step of said processing unit transmits a pre-Symbol first power failure information for each office code stored in the storage unit before Symbol first power failure information power failure information management system other than the power failure information management system which is the source of the When,
From the power failure information management system that is the transmission source of the first power failure information, the processing unit includes second power failure information related to a state change after the occurrence of a power failure , including update information of the power failure occurrence section and information related to power failure recovery. comprising the steps of when the received update in the storage unit the second power failure information received for each of the office code storage,
Wherein the processing unit is, when receiving the acquisition request of the second power failure information from the power failure information management system, those the power failure information managing the latest of the second power failure information for each office code stored in the storage unit Sending to the system ;
Power failure information integration method characterized by including . The power failure information integration method according to claim 3 ,
The processor is
Wherein when the second power failure information and stores the updated in the storage unit for each of the office code, the second power failure information update time and the second power failure information power failure information management system which is the transmission source of the power failure information integration method, which comprises the IP address further stored in the storage unit for each of the office code.