JP2011041416A - Facility data managing method of power system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a facility data managing method of a power system, capable of readily grasping the operating state of facility data, by unitarily managing the facility data at each site. <P>SOLUTION: A wide-area distribution monitoring control system includes a plurality of main computers A equipped with a monitoring control function for a plurality of operation points, and a maintenance computer C which generates facility data to be referenced at execution of the monitoring control function. The maintenance computer C performs management by maintenance subject when generating facility data. The facility data related to a maintenance subject is generated as single source data. When correction of facility data is required, the source data is corrected. The facility data generated based on the source data is distributed to the main computer A as facility data waiting for switching together with operation date and time. The accepted facility data waiting for switching is used for on-line operation instead of facility data being currently used after the date and time of the operation. The maintenance computer C monitors whether or not switching facility data is switched. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a distributed monitoring control system including a plurality of distributed computers such as a power system monitoring control system, and more particularly to a power system including a plurality of computers managed as multi-sites for wide-area decentralization. The present invention relates to a facility data management method.

  The electric power system includes facilities such as a generator, a transmission line, a transformer, and a switch. In such a power system monitoring and control system that monitors and controls the power system, the data relating to these facilities constitutes a record for each type, and furthermore, these records together form a facility database (equipment DB). ing.

  Power system facilities are expanding and becoming more complex every year, and power system monitoring and control systems are required to have higher performance and higher reliability in order to absorb these. Under such circumstances, the power system monitoring and control system employs multiplexing and decentralization of the system and is composed of a plurality of computers. Such a computer group is installed and operated in each operation location.

  Under these circumstances, the recent communication networks have been increased in speed, widened, and the performance and integration of computers have been improved. A plurality of multi-site computers that integrate and execute processing for each of a plurality of operation locations in a single computer are arranged at arbitrary locations. For example, a multi-site A system in A city and a B city A multi-site B system has been installed, and only a human interface computer is placed in the operation location via a wide-area communication network, and the practical use of a system configuration that can easily change the operation system and operation location has been promoted. .

  While the system configuration is complicated, the equipment database held by the power system monitoring and control system must be frequently updated in order to adapt to the power system equipment that changes every day. Moreover, even in a multi-site wide area distributed monitoring and control system, it is necessary to create facility data for each monitoring control operation location, and there is a new establishment, removal, and change of a certain power system facility. In some cases, online information of the power system equipment is required at a plurality of monitoring control operation locations. For example, equipment that is adjacent to and on the boundary line of the monitoring operation location, or power system equipment that is ahead of the boundary line but that is necessary for calculating the power flow of the operation range by taking in-line information on the equipment This is the case. In such a case, it is necessary to perform equipment data maintenance for each operation location. Despite being physically one power system facility, maintenance of the facility database is performed in the same manner as the power system monitoring and control system dedicated to the operation location installed for each operation location.

  In the conventional power system, when there is addition, deletion, or change such as addition of transmission lines, addition of substations, change of capacity, etc., as the maintenance of the equipment database and the switching method of the equipment database, for example, Patent Document 1 There is a technique described in Patent Document 2 and the like.

  This prior art describes the maintenance of the equipment database of the power system monitoring and control system (hereinafter referred to as a single site) and the switching method of the equipment database at a single operation location. In a power system monitoring and control system that is multi-sited as with one site, maintenance is performed on the equipment database dedicated to each operation location, and online monitoring and control operations are performed by switching to the maintained equipment database. It was.

Japanese Patent Laid-Open No. 5-204737 JP 2001-57996 A

  The conventional multi-site facility data maintenance method is a method of managing a single site by a plurality of methods. In other words, it has equipment data for each site, and maintenance source data and object data individually. For this reason, maintenance source data and object data that have been maintained by maintenance operations at any site do not affect the other sites at all. Even if there was, there was a problem that the correction was not reflected.

  In other words, when managing as a multi-site, in general, in terms of operations management, the equipment database etc. must be made into an “integrated management version” and a “site version” that takes into account the unique circumstances of the site. There is a problem of ensuring consistency.

  The present invention is an invention for solving the above-described problems, and provides a facility data management method for a power system capable of centrally managing facility data at each site and easily grasping the operation state of the facility data. For the purpose.

  In order to achieve the above object, a plurality of first computers (for example, main computer A) having a monitoring control function for a plurality of operating locations, and a second facility for creating facility data to be referred to when the monitoring control function is executed. In a wide-area distributed monitoring and control system including a computer (for example, maintenance computer C), a power system equipment data management method in which a second computer creates and manages equipment data, and the second computer When creating data, it is managed using the management subject for maintenance management, and the equipment data associated with the management subject is created as one source data. When the equipment data needs to be revised, the source data is revised and the source data is created. The equipment data created based on the data is distributed to the first computer as equipment data waiting for switching together with the operation date and time, and the first computer accepts the equipment data. Switched waiting for the equipment data to the operation or after the date and time of, and characterized in that the online operation by switching the equipment data in the current operation.

  According to the present invention, the facility data of each site can be centrally managed, and the operation state of the facility data can be easily grasped.

It is a block diagram which shows the system | strain structure of the wide area distributed monitoring control system by this invention. It is a flowchart which shows the process of the maintenance subject management in the multisite by this invention. It is explanatory drawing which shows the example of equipment DB subject status management table. It is explanatory drawing which shows the example (waiting for switching in the site n) of the equipment DB subject status management table 2. It is explanatory drawing which shows the example (switching completion in all the sites) of the equipment DB subject status management table 2. FIG. It is explanatory drawing which shows the example (switchback operation in the site 2) of equipment DB subject status management table 2. FIG. It is a flowchart which shows the process of an equipment DB maintenance subject name management part. It is a flowchart which shows the process of the maintenance subject management in the conventional single site. It is a flowchart which shows the process of the maintenance subject management in the conventional multi site.

  Hereinafter, embodiments for carrying out the present invention (hereinafter referred to as “embodiments”) will be described with reference to the drawings.

  FIG. 1 is a block diagram showing a system configuration of a wide area distributed monitoring control system according to the present invention. With reference to FIG. 1, the facility database maintenance of the wide area distributed monitoring control system by this invention and its database switching method are demonstrated. Note that the wide area distributed monitoring and control system described here is intended for the power system monitoring and control system.

  The power system monitoring and control system includes a main computer A (first computer) that executes monitoring control in the power system online, a test computer B for equipment database maintenance, and a maintenance computer for performing maintenance of the equipment database. C (second computer). The main computer A is installed for each site, and is composed of the main computer A (A10),... Of the site 1, and the main computer A (An0) of the site n.

  The main computer A (A10) at the site 1 includes an online processing unit A11 (101), an online equipment DB (A12) (102) currently in operation, and a future equipment DB (A14) (104) for future use. Accordingly, the facility DB for switching back (A13) (103) for enabling the facility DB for online (A12) (102) to be switched back one generation before, and the facility DB switching unit A15 for switching each facility DB. (105).

  Similarly, the main computer A (An0) at the site n includes an online processing unit An1 (101), an online facility DB (An2) (102) currently in operation, and a future facility DB (An4) (104) for future use. ), Equipment DB (An3) (103) for switching back to enable the online equipment DB (An2) (102) to be switched back to the previous generation if necessary, equipment DB for switching between the respective equipment DBs It has a switching unit An5 (105).

  The maintenance computer C (300) has a function of centrally managing the facility DBs that are held for the number of multi-sites by the conventional multi-site maintenance computer. The maintenance computer C (300) includes an input processing unit 310 for inputting equipment data, an equipment DB development processing unit 308 for developing the input equipment data for a site, and a maintenance subject (management subject) for centrally managing the equipment data. Equipment DB maintenance subject creation unit 304, maintenance subject creation state and operation state management facility DB maintenance subject management unit 303, and future facility DB test transfer processing unit 305 that forwards the future facility DB to the test computer B The future facility DB distribution processing unit 301 for distributing the future facility DB to each site is provided. Further, the maintenance computer C (300) has a future equipment DB (306) for the site 1 which is an equipment DB for each site,..., And a future equipment DB (307) for the site n.

  The facility DB maintenance subject management unit 303 is a facility DB subject state management table 1 (302) (refer to FIG. 3, first facility data management information) for storing the created maintenance subject creation state and operation state. The facility DB subject state management table 2 (311) (refer to FIGS. 4A, 4B, and 4C, second facility data management information) that stores the operation state of the facility DB is managed.

  The test computer B is composed of the test computer B (B10) at the site 1, ..., the test computer B (Bn0) at the site n. The test computer B (B10) includes an online processing unit B11 (201) and a future facility DB (B12) (202) for future use. Similarly, the test computer B (Bn0) has an online processing unit Bn1 (201) and a future facility DB (Bn2) (202) for future use. The test computer B verifies the facility DB by using the future facility DB (202) in the online processing unit 201.

  In addition, the input processing unit 310, the facility DB development processing unit 308, the facility DB maintenance subject creation unit 304, the facility DB maintenance subject management unit 303, the future facility DB test transfer processing unit 305, the future facility of the maintenance computer C (300). The DB distribution processing unit 301 is realized by a program execution process by a CPU (Central Processing Unit). The facility DBs 306 and 307 for the future, the facility DB subject state management table 1 (302), and the facility DB subject state management table 2 (311) are stored in a storage unit such as a hard disk. The maintenance computer C (300) includes a display unit used for displaying messages and the like, and includes a CRT (Cathode Ray Tube), a liquid crystal display, and the like. It also has input units such as a keyboard and a mouse.

  Similarly, the online processing unit 101 and the facility DB switching unit 105 of the main computer A are realized by program execution processing by the CPU. The online facility DB 102, the switchback facility DB 103, and the future facility DB 104 are stored in a storage unit such as a hard disk. The online processing unit 201 of the test computer B is realized by a program execution process by the CPU. The future facility DB 202 is stored in a storage unit such as a hard disk.

  FIG. 2 is a flowchart showing the maintenance subject management processing at the multi-site according to the present invention. Reference is made to FIG. 1 as appropriate. An object of the present invention is to manage facility data by maintenance subject management.

  First, the administrator inputs and registers a subject of equipment data maintenance that requires maintenance of equipment data in the input processing unit 310 (step S1, “subject registration”). As the maintenance subject, a word indicating an arbitrary maintenance content and a facility to be maintained, for example, the name of an electric power station are input. In addition, in the registration contents, the operation start date and maintenance contents of the maintenance subject are also registered.

  Next, the administrator inputs the facility source data 309 or corrects the already-entered facility source data (Step S2, “Input”). The actual correction content for the subject is input, and the equipment source data 309 is created. The equipment source data 309 here is actually saved in a format that cannot be used by a computer as it is.

  Upon receipt of the input completion request, the facility DB development processing unit 308 executes “development” processing to obtain a data state that can be recognized by the computer processing (step S3, “development”). “Development” means that the facility source data 309 is processed (converted) into a form usable by a computer. If there is an abnormality in the format of the equipment source data 309 as a result of the expansion, the process returns to the “input” state in step S2, and the input of the correction content is reviewed and expanded again in step S3. If the development result is normal, a form that can be recognized by the computer (hereinafter referred to as equipment data) is created.

  In the development process, the equipment DB development processing unit 308 reflects the future equipment DBs 306 and 307, which are equipment databases of adjacent sites, through the site to which the maintained equipment belongs and the transmission line equipment. By adding affiliation site information to the equipment source data 309, it can be reflected only in the related equipment database.

  The future facility DB test transfer processing unit 305 reflects and updates the deployed future facility DBs 306 and 307 in the future facility DB 202 of the related site of the test computer B. The reflection update is automatically performed when the “development” in step S3 is completed.

  The test computer B (B10) of the site 1 which is the test computer B,..., The test computer B (Bn0) of the site n confirms the test of the related site with the test simulated online data (step S4, “ test"). Specifically, the created facility data is transferred to the test computer B, and whether or not there is any problem in online operation, test data regarding the state of the modified facility, for example, switch ON / OFF, switch current, voltage Input the data that simulates and confirm whether there is no problem with the created data. If there is a problem in the test in step S4, the test computer B notifies the maintenance computer C, and the process returns to step S2. That is, it returns to the input state of equipment source data, re-reviews and creates it, and performs "deployment" in step S3 and "test" in step S4 again.

  In step S4, when the “test” is completed, the test computer B is in a state in which the maintenance subject can be transferred to the main computer A, and the future facility DB distribution of the maintenance computer C (300). The processing unit 301 is notified (step S5, “waiting for delivery”). The creation of the maintenance facility database is completed in the “waiting for delivery” state in step S5. That is, the creation of a future facility database that can be used online by the main computer A is completed.

  As described above, the maintenance computer C (300) has one facility source data 309, and has one facility database to be created for multiple sites. A facility database for the future can be created with the subject.

  Although the creation of the future equipment database created with one maintenance subject has been completed, to use it online, the future equipment database created in the future equipment DB (104) of the multi-site main computer A And the equipment database needs to be switched to the equipment database in operation.

  The future facility DB distribution processing unit 301 converts the future facility DBs 306 and 307, which are individual facility databases corresponding to the respective sites, created with the maintenance subject in “waiting for distribution” in step S5 to the main computer A. To the future facility DB (104) for the site (step S6, "preparation for switching").

  In step S6, the future facility DB (104) at each site of the main computer A is the same as the future facility database created by the maintenance computer B, and is in the latest state. In order to actually use the maintenance subject in the state of “preparation for switching” in step S6 online, each online facility DB (102) of each site is changed to each future facility DB (104). It is necessary to switch by the equipment DB switching unit 105.

  When switching is performed after the operation date and time on the site side, operation by the future facility DB (104) is started (step S7, “in operation”). That is, in step S7, on the date and time when the operation is started, the facility data currently in operation and the facility data in the switching preparation state are switched, the facility data in the switching preparation state is set to the operating state, and the maintenance subject is completed. .

  Each site performs its own operation, and the maintained DB for future use (104) may be necessary at site 1 depending on the current operation state, and may not be necessary at site n for the time being. For this reason, whether or not the status of the maintenance subject that has reached the “switching ready” state is switched to the operational state needs to be managed for each site thereafter.

  After step S7, the administrator on the site side may perform a switchback operation using the switchback facility DB (103) due to a problem or the like (step S8, “switchback operation”). That is, when a problem occurs in online processing using the equipment data created with the maintenance subject in operation, in step S8, the equipment data is returned to the switch-back equipment DB 103 which is the equipment data of the previous generation. It is preferable to wait for correction input of the source data 309.

  Since each site may be operated independently, the maintenance computer C (300) monitors the state of the equipment DB at each site. For example, the maintenance computer C (300) issues a confirmation request to the main computer A at each site in order to confirm the state of the equipment DB used in online processing. The main computer A of each site that has received the confirmation request transmits the equipment DB subject No. (subject number) in operation to the maintenance computer C (300). The received maintenance computer C (300) updates the equipment DB subject state management table 1 (302) and the equipment DB subject state management table 2 (311). In addition, the main computer A of each site may transmit equipment DB subject No. to the maintenance computer C (300) regularly (for every predetermined time).

  When the maintenance computer C (300) confirms that the switchback operation has been performed, it notifies the administrator. The administrator of the maintenance computer C (300), after confirming at which site the switchback operation was performed, contacts the administrator of each site, creates an improvement plan for the equipment DB, and returns to step S1 again. Perform a new “subject registration”.

  The facility data management method of this embodiment manages the maintenance subject used in the multi-site, and manages from the “subject registration” in step S1 to the “waiting for delivery” state in step S5 in one state. The process from “switching preparation” in step S6 to “switchback operation” in step S8 is managed for each site. In addition, the facility data management method can monitor the state of each site on the maintenance computer C (300) side and grasp the failure state of the facility DB from the switching state of the facility DB.

As a comparative example, conventional maintenance subject management at a single site and multiple sites will be described with reference to FIGS.
FIG. 6 is a flowchart showing a conventional process for managing a maintenance subject at a single site. The maintenance subject is managed by the site, and “subject registration” in step S1, “input” in step S2, “development” in step S3, “test” in step S4, “waiting for delivery” in step S5, step S6 “Switching preparation”, step S7 “in operation”, and step S8 “switchback operation”.

  FIG. 7 is a flowchart showing a conventional maintenance site management process in a multi-site. This is a collection of the same processes as in the single site shown in FIG. In other words, if maintenance title management is applied to each site, maintenance of facility data that has been converted into multi-sites can be performed in the same way as a conventional single site. However, since it is not managed with a unified maintenance subject, the fact is that a plurality of sites linked in the power system are managed with different maintenance subjects.

Next, a table for managing the creation state and operation state of the equipment DB will be described.
FIG. 3 is an explanatory diagram illustrating an example of the equipment DB subject state management table 1. The equipment DB subject status management table 1 (302) is managed in units of maintenance subject (management subject), and includes a maintenance subject subject number, a maintenance subject, an operation date and time, the DB creation state, the DB operation state, and the like. For example, from the record 3021, the maintenance subject is “A” and the subject No is “1”. The operation date and time is April 1, 2009 (time omitted), the creation status of the DB is “waiting for switching”, and the operation status is all “operating” at the distributed site. Further, from the record 3022, the maintenance subject is “B” and the subject No is “2”. The operation date and time is May 1, 2009, the creation status of the DB is “Waiting for switching”, and the operating state is that any of the distributed sites is “Preparing for switching” and “Waiting for switching”. Further, from the record 3023, the maintenance subject is “C” and the subject No is “3”. The operation date and time is scheduled to start operation on June 1, 2009, and it can be seen that the creation state of the DB is “input”.

  FIG. 4A is an explanatory diagram showing an example of the equipment DB subject state management table 2 (waiting for switching at site n). FIG. 4B is an explanatory diagram illustrating an example of the facility DB subject state management table 2 (switching is completed at all sites). FIG. 4C is an explanatory diagram illustrating an example of the equipment DB subject state management table 2 (switching operation at the site 2). The equipment DB subject status management table 2 (311) shows the operation status of the equipment DB, manages the maintenance DB created with the maintenance subject for each site by managing the subject No. in operation, It is also a table for managing under which maintenance subject data for future facility data is created.

  The equipment DB subject state management table 2 (311) shown in FIG. 4A to FIG. 4C is a state table for managing the operation state of the equipment DB, and is being operated in the site No, the DB switching waiting subject No, and the site No. Consists of subject number and the like. The DB switching waiting subject number is associated (linked) with the subject number in FIG.

  In FIG. 4A, DB switching waiting subject No. “2” of each site (maintenance subject “B”. On the other hand, in Site 1, the subject No. in operation is “2”, but Site n is in operation. It can be seen that the subject No. remains “1”.

  FIG. 4B shows a case where the operation state of the site n is changed from FIG. 4A. In contrast to the DB switching waiting subject number “2” (corresponding to the maintenance subject “B”), the in-operation subject No. is “2” in all sites. In this case, the facility DB maintenance subject management unit 303 updates the change of the DB operation state from “Waiting for switching” to “In operation” in the record 3022 of the facility DB subject state management table 1 (302).

  FIG. 4C shows a state when a switchback operation occurs in the site 2 from the state of FIG. 4B. In the case of the state of FIG. 4C, in the site 2, the operating subject number is changed from “2” to “1”, and it can be seen that some trouble has occurred on the site 2 side.

  FIG. 5 is a flowchart showing processing of the equipment DB maintenance subject management unit. The process shown in FIG. 5 is a process for monitoring the operation state of the site of the facility DB maintenance subject management unit 303. Specifically, (1) when there is a subject number for waiting for switching, if the site does not operate even after a predetermined time has elapsed from the operation start date and time, (2) if switchback operation occurs at the site, the maintenance computer There are a process for notifying the administrator of C (300) and a process for updating the operation status of each site to the management table. Hereinafter, “equipment DB subject state management table 1” is referred to as “management table 1”, and “equipment DB subject state management table 2” is referred to as “management table 2”.

  The facility DB maintenance subject management unit 303 repeats the aggregation of information on the operation state of the facility DB at regular time intervals (every predetermined time) (step S501). By repeatedly collecting information on the operation state of the facility DB at regular intervals, the latest information on the operation state of the facility DB can be obtained. The facility DB maintenance subject management unit 303 repeats the process of collecting information on the operation state of the facility DB for the main computers A at all sites managed by the maintenance computer C (300) (step S502).

  The facility DB maintenance subject management unit 303 issues a confirmation request to the facility DB switching unit 105 of the main computer A at each site. The main computer A at each site that has received the confirmation request transmits an operating subject No. (subject number) that is the subject No. of the operating equipment DB to the maintenance computer C (300). The maintenance computer C (300) receives the operating subject number No (step S503). Then, it is determined whether the switching waiting No in the management table 2 (311) is different from the received in-operation subject number (step S504). If they are different (step S504, Yes), it is determined whether or not a predetermined time has elapsed from the operation date (step S505). If the predetermined time has elapsed (step S505, Yes), the facility DB maintenance subject management unit 303 notifies (notifies) the administrator (step S506), and proceeds to step S507. As a notification method, for example, the contents of the management table 2 may be displayed on a display unit of a terminal received by the administrator, or a portable terminal owned by the administrator may be contacted. In step S505, if the predetermined time has not elapsed (step S505, No), the process proceeds to step S507.

  In step S507, the facility DB maintenance subject management unit 303 refers to the management table 2 (311) and determines whether or not a switchback has occurred (step S507). When switchback has occurred (Yes in step S507), the equipment DB maintenance subject management unit 303 notifies (notifies) the administrator (step S508), and proceeds to step S509. The determination of whether or not the switchback has occurred is made with reference to FIG. 4B. For example, when the in-operation subject number of the site 2 is changed from “2” to “1”, it is determined that a switchback has occurred. If no switchback has occurred in step S507 (No in step S507), the process proceeds to step S509.

  Further, in step S504, when the facility DB maintenance subject management unit 303 determines that the subject subject No in waiting for switching in the management table 2 (311) is the same as the subject No in receiving operation (step S504, No), step S509. Proceed to

  In step S509, the facility DB maintenance subject management unit 303 determines whether the subject No in operation is switched. When there is switching (step S509, Yes), the management table 2 (311) is updated (step S510), and the process proceeds to step S511. Specifically, in the state shown in FIG. 4A, when a subject No. “2” in operation at site n is received, it is assumed that switching has occurred, and the subject No. in operation at site n is changed from “1” to “1” as shown in FIG. Update to 2 ”. If there is no switching (No in step S509), the process proceeds to step S511.

  In step S511, the facility DB maintenance subject management unit 303 determines whether or not switching of all related sites has been completed. When all the switching is completed (step S511, Yes), the management table 1 (302) is updated (step S512), and the process returns to step S502. Specifically, in FIG. 4B, when the in-operation subject numbers are all “2” in the site 1 to the site n, the DB operation state of the record 3022 in FIG. Update to In step S511, when all the switching has not been completed (step S511, No), the process returns to step S502.

  The maintenance computer C (second computer) of the present embodiment associates the management number of the management subject, the operation date and time, the creation state of the facility data, and the operation state of the facility data with the first facility data management information ( For example, the second equipment data is stored in the storage unit as the equipment DB subject state management table 1 (302), and the management number of equipment data waiting to be switched is associated with the management number of equipment data being operated in the main computer. It memorize | stores in a memory | storage part as management information (for example, equipment DB subject status management table 2 (311)).

  When the second computer of the present embodiment receives the management number of the facility data in operation at a predetermined time from the main computer, the second computer switches with reference to the first facility data management information and the second facility data management information. When it is determined that the waiting facility data has not been switched for a predetermined time, the display unit is notified that switching has not been performed.

  When the second computer of the present embodiment receives the management number of the equipment data in operation at every predetermined time from the main computer, the management number of the received equipment data is referred to the second equipment data management information, When it is determined that the management number is older than the previously operated management number, the display unit notifies that the facility data has been switched back.

  According to the power system equipment data management method of the present embodiment, the maintenance subject management can be centrally managed at the equipment database creation stage without depending on the site, and the created equipment database is operated at the site. Can be managed for each.

  The power system facility data management method of the present embodiment makes it possible to consolidate maintenance subject management at the database creation stage even in a multi-site, and even if there are facilities commonly used for each site, 1 Data can be corrected by one-time maintenance, saving labor. In addition, it is possible to switch the operation of the equipment database created according to the operation status when necessary for each site.

  The maintenance computer C (second computer) monitors the operation state of the facility database at each site. (1) Even if the facility data distributed to the site side has a predetermined time from the operation start date and time, the site side If it is not operated, it can be notified on the display unit of the second computer. (2) When a switchback operation occurs on the site side, it can be notified to the display unit of the second computer.

101 Online processing unit 102 Online equipment DB
103 Equipment DB for switchback
104 Future Equipment DB
105 Equipment DB switching unit 201 Online processing unit 202 Future equipment DB
300, C Maintenance computer (second computer)
301 Future Equipment DB Distribution Processing Unit 302 Equipment DB Subject State Management Table 1 (First Equipment Data Management Information)
303 Facility DB Maintenance Subject Management Unit 304 Facility DB Maintenance Subject Creation Unit 305 Future Facility DB Test Transfer Processing Unit 306,307 Future Facility DB
308 Equipment DB development processing section 309 Equipment source data 310 Input processing section 311 Equipment DB subject state management table 2 (second equipment data management information)
A Main computer (first computer)
B Test calculator

Claims (5)

In a wide area distributed monitoring and control system comprising a plurality of first computers having a monitoring control function for a plurality of operating locations, and a second computer for creating facility data to be referred to when executing the processing of the monitoring control function, A power system equipment data management method in which the second computer creates and manages the equipment data,
The second computer manages the management data with a management subject for maintenance management when creating the equipment data, creates the equipment data associated with the management subject as one source data, and corrects the equipment data. When necessary, modify the source data, and distribute the equipment data created based on the source data to the first computer as equipment data waiting for switching together with the operation date and time,
The first computer switches the received facility data waiting for switching to the currently operating facility data after the operation date and time, and operates the system online. The second calculator is
Storing the management number of the management subject, the operation date and time, the creation state of the facility data, and the operation state of the facility data in the storage unit as first facility data management information;
The management number of the facility data waiting for switching and the management number of the facility data being operated in the first computer are associated with each other and stored in the storage unit as second facility data management information. Item 2. The power system facility data management method according to Item 1. The second calculator is
When the management number of the equipment data being operated is received from the first computer every predetermined time, the equipment data waiting for switching is referred to by referring to the first equipment data management information and the second equipment data management information When it is determined that the switch has not been switched for a predetermined time, the display unit is notified that the switch has not been performed. The facility data management method for the power system according to claim 2. The second calculator is
When receiving the management number of the equipment data in operation at a predetermined time from the first computer, the management number of the received equipment data was previously operated with reference to the second equipment data management information. The power system equipment data management method according to claim 2, wherein when it is determined that the equipment number is older than the management number, the display section notifies that the equipment data has been switched back. The power management system data management method according to claim 1, wherein the management subject is a word indicating arbitrary maintenance content or a name of a facility to be maintained.

Images