JP2000039944A - Maintenance system and method therefor and storage medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent a development error by operating logical check in response to a demand for the registration of maintenance data, and registering the maintenance data in a registering means when any problem is not present. SOLUTION: When maintenance data are developed, and a distribution diagram is displayed, and a screen operation is executed, the update processing of the system diagram is operated in response to this. When an operator ends the maintenance processing, the recording of the screen operation is outputted as text data for each case, and registered in a distribution server as maintenance data. Also, at the time of developing the maintenance data, the maintenance data are converted into a program format, and a differential program is generated. When this differential program is executed, the processing operated by an operator is quickly reproduced, and the updated system diagram is displayed. The processing operated by the operator is recorded in those maintenance data, and link information to a new facility is generated at the time of executing the differential program. Therefore, even when the development order is exchanged, any development error due to the abnormality of the link can not be generated.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a distribution system monitoring and control system, and more particularly to maintenance of a distribution line system.

[0002]

2. Description of the Related Art A distribution system monitoring and control system is used as a system for managing and maintaining the distribution line system performed by a power company. Maintenance here refers to changing distribution equipment, such as replacing distribution lines or adding new equipment.
The situation changes every day due to maintenance such as the construction of new homes and the extension of distribution lines and new switches.

[0003] In order to manage the power distribution system and understand the situation, before performing maintenance,
First, the contents of the construction plan, such as where and what equipment to install, are registered in the monitoring control system in advance. This planning is performed using the maintenance system of the distribution system monitoring and control system.

[0004] The operator of the system for making a construction plan confirms the state of charging and stopping of power while checking the map of the construction site and the route diagram showing the distribution system displayed on the screen of the system, and extends the wiring or connects the equipment. Perform a screen operation such as arranging the symbols shown on the battlefield to construct a construction plan.

This maintenance system divides a distribution line from a power plant or a substation to a consumer such as a general household into a plurality of areas, and determines a display color or a blinking display in units of sections or distribution lines. Separately, a graph showing the electrical connection on the map showing the construction site and a diagram showing the actual attachment position are displayed on the screen of the system. This display screen expands the maintenance data of the other works performed up to the construction date with respect to the data (base data) that is currently registered in the system, and shows the power distribution system on the construction day. A system diagram is generated and displayed.

The operator changes the power distribution system diagram on the display screen by adding a new facility using an MMI (man-machine interface) such as a mouse, and determines the location of the facility.

When the operator installs new equipment on the system diagram on the display screen, the system obtains an electrical connection state (node branch) based on the change in the system diagram, and Automatically recognize connections and generate equipment data. When the operator continues the screen operation and makes a plan, the maintenance data of the power distribution system diagram is registered in the system by the subject of this construction. The maintenance data is extracted from the distribution system diagram before being changed by the maintenance, and is registered in the system in the form of difference data indicating how the maintenance data has been changed by the maintenance.

FIG. 10 is a diagram for explaining the maintenance data. In FIG. 10, it is assumed that the maintenance work of the subject A1 is performed for the state registered in the system, and then the maintenance work of the subject A2 is performed.

[0009] The construction of the subject A1 is based on the wiring line1 between the switch SW0 and the telephone pole P0 for the distribution system based on the base data registered in the distribution system monitoring and control system.
It is assumed that a switch SW1 is newly provided above. In this case, the operator places the switch SW1 at an appropriate place on the wiring line1 using a mouse or the like on the screen. Then, the system registers the switch SW1 as background processing together with the screen display change processing,
e1 is deleted from the registration, and instead, the line 2 between SW0 and SW1 and the line 3 between SW1 and P0 are additionally registered. Deletion of line 1 and addition registration of SW 1 and lines 2 and 3 which are the result of this change are performed by subject A 1
Register as maintenance data.

It is assumed that the construction of the subject A2 is to newly install a switch SW2 on the wiring line3 between the switch SW1 and the telephone pole P0 after the construction of the subject A1 at the same site as the subject A1. In this case, in the system diagram in which the maintenance data of the subject A1 is developed in the base data, the operator operates the switch SW2
Is placed at an appropriate location on the wiring line3, the system performs a process of changing the screen display, a registration of the switch SW2 as a background process, a deletion of the registration of the wiring line3, a wiring line4 between SW1 and SW2, and S.
The wiring line5 between W2 and P0 is additionally registered.
Then, the deletion of line3 and the additional registration of SW2 and lines 4, 5 which are the result of this change are registered in the system as maintenance data of the subject A2.

[0011] These operations also update the data for the equipment on the system diagram. In the wiring system diagram, facility numbers are assigned to the facilities on the system diagram, and information on each facility is managed. For each facility, the facility number is used to register data for the facility, such as the location where each facility is installed, its type, facility input (range capacity), switch (inclination (angle)) and the like, and link information. This link information is information indicating to which other facility the facility is connected. For example, the SW2 in FIG. 10 stores line4 and line5 as the link information.

FIG. 11 is a diagram for explaining the update of data for wiring and switches in the system diagram registered and changed by the construction under the subject names A1 and A2 in FIG. In FIG. 11, equipment numbers from 100 to 104 are assigned to the wiring, and equipment numbers from 50 to 54 are assigned to the switches.
1 is set to 100, and SW0 is set to 50. The storage area corresponding to each equipment number stores data such as link information and installation position for that equipment.

When the operator attaches new equipment to the wiring diagram on the display screen by using a mouse or the like, data of the equipment on the wiring diagram is deleted or registered. For example, when the operator places SW1 on line1 as maintenance of the subject A1, the system registers the SW1 in the vacant 51 with the equipment number of the switch, deletes the registration of line1 in which SW1 is hit, and replaces it. Are registered in the vacant 100 and 101 with the wiring facility number. In the case of the subject A2, when the operator puts the SW2 on the line 3 on the screen while the maintenance data of the subject A1 is expanded in the base data, the SW2 is registered in the vacant facility number 52. Then, the line 3 hitting the SW 2 is deleted, and the lines 4 and 5 are registered in the registration numbers 101 and 102.

[0014]

Since maintenance work is performed frequently and may be changed several times between the planning and the actual work, the maintenance data at the time of planning the work is required. The registration is temporarily registered in the form of difference data, and upon receiving a notification that the construction has been completed, the maintenance data is called from the subject of the construction and the main registration is made. The main registration is performed by expanding the maintenance data of the subject into base data registered in a power distribution server described later, and updating and registering this as new base data.

However, each maintenance work is not always performed as scheduled. For example, the work that should have been performed earlier may be postponed due to the weather, and the order of the work may be changed. In such a case, in the main registration of the maintenance data after the completion of the construction, the development of the maintenance data of the construction that should be performed later is performed on the base data before the maintenance data of the preceding construction is developed. Will be.

FIG. 12 is a diagram showing an example in that case.
FIG. 12 illustrates a case where the maintenance data of the subject A2 is expanded to the base data without expanding the maintenance data of the subject A1 of FIG.

As shown in FIG. 10, the maintenance data of the subject A2 is difference data indicating a change such as a new addition or deletion of a facility from the diagram in which the maintenance data of the subject A1 is developed. Therefore, if this is expanded with respect to the base data, an error occurs. For example, there is no difference data of the subject A2 for the wiring line1.
1 remains as it is, and line 4 is a switch SW in the storage area corresponding to the facility number 101 as facility link information.
Although data indicating 1 and SW2 are stored, SW1 is not present in the base data from which the data is developed. Therefore, if the maintenance data of the subject A2 is directly expanded into the base data, the connection state is as shown in FIG. 12 and an expansion error occurs.

[0018] Even if a systematic diagram as shown in Fig. 12 occurs and a deployment error occurs, it is not clear from this figure where the problem has occurred in the equipment link. In the logic check, if there is a logical inconsistency and an abnormality is found, the corresponding device is displayed in a different color, but in the case of a deployment error due to such an equipment link error, the color is changed and the abnormal part is clearly identified. Hard to show. Therefore, in such a case, the operator performs the maintenance process again and regenerates the maintenance data.

Further, the conventional method has the following problem.
The maintenance of the power distribution system is performed in such a manner that a maintenance area is divided into a certain area, a sales office is set up in each area, and each sales office performs construction in the area in charge.

The current distribution system monitoring and control system is
There has been proposed a configuration in which client devices constituting a system are installed in each sales office, and a power distribution server installed in a center that controls the entire system is connected via a network. And in such a configuration, the maintenance data from the maintenance
The data is sent to the power distribution server via the network, and the management control of all maintenance data is performed by the power distribution server.

FIG. 13 is a diagram showing a configuration of a conventional distribution system monitoring system. The distribution server stores the maintenance data of the previous sales office in a database and stores it.When performing maintenance processing at each sales office, the base data stored on the distribution server and the sales office adjacent to the site where construction is performed are performed. The maintenance data of other works performed by the work day on which the work is performed are read out via the network. When the maintenance process is completed, the maintenance data is temporarily registered in the power distribution server.

By storing all the maintenance data in the power distribution server and reading the necessary data from the power distribution server in this manner, the maintenance data of another business office can be referred to from the power distribution server. .
In the case of FIG. 13, the adjacent A office and B office can read out each other's maintenance data from the power distribution server and expand it as needed. However, in such a configuration, the following problem occurs.

In the power distribution server, when there is a request for the main registration of the maintenance data from the sales office, the maintenance data is developed into the base data to perform a logic check and then perform the main registration. However, when a plurality of maintenance data created in another sales office is expanded for logical check, 1
There is a case where a deployment error occurs when trying to set a plurality of facilities for one facility number.

FIG. 14 is a diagram for explaining a case where the equipment number is duplicated at the time of development. As shown in FIG. 11, when a new facility is registered, a facility number that is unused at that time is set in the facility. The setting of the equipment number is performed as a background process simultaneously with the screen operation by the operator, and the unused equipment number is checked at that time. Accordingly, as shown in FIG. 14, a switch SW1 is installed on the wiring line1 at the sales office A for maintenance of the subject A1 and a switch SW2 is installed on the line1 as maintenance processing of the subject B1 at the sales office B for the base data as shown in FIG. Suppose that maintenance processing is performed, the equipment data is newly installed and the equipment numbers are set for SW1 and SW2 in the maintenance data of these maintenance processings. Is set. Therefore, as shown in FIG. 14, the equipment number 51 is set to SW1 in the maintenance data of the subject A1 of the office A, and the equipment number 51 is also set to SW2 in the maintenance data of the subject B1 of the office B.

Therefore, when these are temporarily registered, if the maintenance server develops both maintenance data for the logical check, the maintenance data that is later developed will be the equipment already used at the time of the development. Attempting to allocate new equipment to a number results in a deployment error. For example, when the maintenance data of the subject B1 is registered after the maintenance data of the subject A1 is registered, a deployment error occurs when the facility number 51 already set in the SW1 is newly set in the SW2 at the time of the deployment.

As described above, in the maintenance processing performed at another sales office, the equipment numbers are independently set to the new equipment, and when these maintenance data are expanded, a plurality of equipments are duplicated at the same equipment number. An expansion error may occur due to the setting.

An object of the present invention is to provide a maintenance system that takes the above problems into consideration.

[0028]

A maintenance system according to the present invention comprises a plurality of client devices connected to a server via a network.

Each client device includes a screen generation unit, an operation storage unit, and a registration request unit. The screen generating means generates a distribution system diagram on the screen.

An operation receiving means and an operation storage means for receiving an operation by the operator with respect to the power distribution system diagram sequentially store the operations by the operator. The registration requesting unit requests the server to store data indicating the operation stored in the operation storage unit as maintenance data.

The server includes a registration unit and a registration processing unit. The registration unit registers the maintenance data in a database. This maintenance data indicates, for example, an update routine called in response to an operation by an operator.

Further, the system may further comprise a difference program generating means for compiling the maintenance data and generating a difference program for reproducing the operation by the operator.

Also, the present invention can be configured as a computer-readable storage medium storing a maintenance method and a computer program in a power distribution system.

According to the present invention, since the maintenance data is data indicating an operation by the operator, link information is generated when the maintenance data is developed, so that a development error due to abnormal link information does not occur. Further, since the equipment number is also set when the maintenance data is expanded, there is no possibility that a plurality of equipment is set for one number.

[0035]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below. The maintenance system according to the present embodiment uses maintenance data of a maintenance work plan created by performing operations such as extending wiring and placing symbols indicating devices on the power distribution system diagram displayed on the screen. Rather than handling in the form of difference data as described above, it is characterized in that it is handled as the form of a difference program that reproduces the operation process performed on the system diagram on the screen during the maintenance process.

FIG. 1 is a diagram for explaining maintenance data in this embodiment. In FIG. 1 (a), the operator is shown in FIG. 10 with respect to the power distribution system diagram displayed on the screen.
It is assumed that the same operation as that of the construction of the subjects A1 and A2 was performed.

In the operation for the construction of the subject 1, when the operator places a symbol indicating the switch SW1 at an arbitrary position on the wiring line 1 displayed on the screen, the system responds accordingly and the back-up is performed in the same manner as in FIG. As the ground processing, the switch SW1 is registered and the wiring l
ne1 is deleted from the registration, and the line line2 between SW0 and SW1 and the line3 between SW1 and P0 are replaced.
Register additionally. With the change of the wiring system diagram, the electrical connection state (node branch) is obtained and automatically changed.

The operations performed by the operator for changing the distribution system diagram, such as the arrangement of the equipment, are all stored, including the order. For example, even if the operator first installs a new SW1 and then deletes the SW1, both are stored in order.

When the operator finishes the maintenance processing of the subject and saves the processing result as maintenance data, the text format of a program (difference program) for reproducing the processing performed by the operator on the power distribution system diagram on the display screen And output.

The output format of the difference program is, for example, output as text data expressed by a function or a subroutine indicating a screen operation of an operator as shown in FIG.
In the case of FIG. 1, the difference program of the subject A1 is output in a form in which a switch type SW1 and its installation positions X1 and Y1 are given as parameters to a function Add_SW for installing the switches. Similarly, as the difference program of the subject A2, the switch type S
It outputs as a function Add_SW for installing a switch having W2 and its installation positions X2 and Y2. In FIG. 1,
The parameters given to the functions are representative ones for the sake of simplicity, and are not limited to these.

The operations performed by these operators on the system diagram on the screen are converted into text data indicating the corresponding functions and output as maintenance data. When converting the data into text data and outputting it, a logic check may be performed, and the duplication operation may be deleted to perform data compression.

When the operator performs operation processing on the distribution system diagram displayed on the screen, such as installing equipment on the screen, the system calls the corresponding update routine at that moment, and the update routine draws the drawing. In addition, as background processing, for example, in the case of installation of equipment, determination is made as to which wiring the installation position is hit, registration / deletion processing of equipment and wiring, change of electrical connection, and the like. A function typified by Add_SW represents these called update routines. One maintenance data is expressed as a group of functions corresponding to the number of screen operations by the operator. Also, if there is a change in the plan and the maintenance data already created is modified later, the text data of the function indicating the operation process performed by the operator for the modification is added to the end of the maintenance data before the modification. It is output in an appended form.

The maintenance data in the text data format is temporarily registered in the power distribution server with the subject of the maintenance work. Next, the maintenance data expanding process will be described.

Since the maintenance data is text data indicating a function or a subroutine indicating an operation performed by an operator, it is compiled as a data source program by a general-purpose compiler.
A difference program that reproduces the operation of the operator can be generated. By executing the generated difference program, the processing performed on the distribution system diagram by the operator can be reproduced, and maintenance data can be developed. .

FIG. 2 is a diagram showing a source program of the difference program. FIG. 2 shows a format when compiling by a C language compiler. For text data output in the form of a function or subroutine as shown in FIG. 1, main () is added to the beginning or end as shown in FIG.
If the format is adjusted to match the format of the language, such as adding ｛｝ or ｛｝, it can be compiled with a general-purpose compiler, and a difference program can be generated.

The generated difference program serves to call an update routine and transfer parameters to the routine. The update routine itself is already provided in the system and is used when an operator performs a screen operation. Is what is done. Therefore, the maintenance data is converted to a text format, and the distribution server or each client device at each sales office compiles the data in a text format. For example, the distribution server and each client device use different CPUs and OSs. However, the problem of data compatibility with the maintenance data does not occur.

Also, the maintenance data in the form of the difference program differs from the format of the difference data in that the maintenance data itself has no link information, and when executed as a difference program, the link information is generated. Since the numbers are set, even if the order of development is changed or maintenance data of a different office is developed, no development error occurs due to duplication of link information or equipment number.

FIG. 1B shows the maintenance data in this embodiment in which the order of development is changed.
It is a figure showing the case where only maintenance data of subject A2 of (a) was developed.

Since the maintenance data of this embodiment is of the difference program type, when the difference program of the subject A2 is executed, a process for setting the switch SW2 at the position of X2, Y2 on the screen is started.

This maintenance data stores only the action performed by the operator on the system diagram on the display screen, that is, the action of placing the switch SW2 at the position X2, Y2. Therefore, processing for realizing this action is performed when the difference program generated from the maintenance data is executed. That is, this SW
2 is checked, and the wiring in which SW2 is hit is checked, and the wiring line1 is deleted and a substitute wiring line is deleted.
The process of registering 2 and 3 is performed by executing this difference program and calling and processing a routine such as Add_SW for changing the system diagram.

Therefore, even if the order in which the maintenance data is developed is changed, the maintenance data can be developed without causing a development error due to the abnormal link information as shown in FIG. Even if a deployment error such as installation of a facility in a place where there is no wiring occurs, these can be color-changed to clearly indicate an abnormal part. Furthermore, when executing the difference program to develop the maintenance data, the equipment number is set for the new equipment, so there is no need to set up multiple facilities with the same number, and the equipment at the office boundary And data on equipment maintenance at locations near both sales offices can be deployed without any problems.

FIG. 3 is a diagram showing an overall flow of the maintenance processing of the present embodiment. In the present embodiment, first, the maintenance data is developed on the base data read from the power distribution server, and the power distribution system diagram is displayed on the CRT screen.
When various screen operations are performed on this display screen using a mouse or the like, a data update routine corresponding to the operation is called, and processing for updating the system diagram is performed.

When the operator finishes the maintenance processing, a record of the screen operation performed by the operator is output as text data for each case, and this is registered in the power distribution server as maintenance data.

When the maintenance data is developed, the maintenance data is converted into a program format, such as compiling, to generate a difference program. When the difference program is executed, the processing performed by the operator on the system diagram displayed on the screen is reproduced at high speed, and the updated system diagram is displayed on the screen.

These maintenance data record the processing performed by the operator on the power distribution system diagram on the display screen, and link information and the like to the new equipment are generated when this difference program is executed. Therefore, even if the order of development is changed, a development error due to a link error does not occur.

FIG. 4 is a flowchart showing a process performed by a client device installed at each business office. The client device first receives a command from the operator in step S1, and then determines the type of command in step S2. If the instruction is a request for a maintenance process, the process proceeds to a maintenance process in step S3. If the command is a request for registration of the maintenance data to the server, the process proceeds to a registration process in step S4. If the request is a termination request, the processing is terminated.

FIG. 5 is a flowchart showing the maintenance processing in step S3 of FIG. When the maintenance process is started, first, in step S11, the operator requests the operator to input a subject of the maintenance work for performing the maintenance process, and receives it.

Next, as step S12, base data and maintenance data of another business office are read from the power distribution server. Then, in step S13, the maintenance data of the other business office is processed into a format of a compiler used by itself, and this is compiled to generate a difference program. Then, as step S14, these are sequentially executed and expanded together with the self maintenance difference program. As a result, a distribution system diagram in which each maintenance data is developed is generated on the CRT screen of the client device.

When the operator performs an update operation such as installation of a new facility with the mouse or the like on the power distribution system diagram displayed on this screen, the client apparatus executes step S1.
As 5, the corresponding update routine is called, and the process corresponding to the operation is performed. These operations are sequentially stored in the memory as step S16. The processes in steps S15 and S16 are repeated until the operator ends the maintenance process (step S17,
N).

The operator completes the update of the distribution system diagram,
When the maintenance processing is completed (step S17,
Y) Next, the client device converts the operation of the operator stored and accumulated in the memory into text data (step S18).

It is determined in step S whether or not this maintenance processing is for new maintenance.
(Step S1)
9) If it is new (step S19, new),
In step S20, a file is newly created with this subject, and the operation of the operator who converted the text data in step S18 into this file is output to this file.

If it is determined in step S19 that the maintenance processing is to further update the existing maintenance data, the operation of the operator converted to the text data in step S18 is performed in step S11 in step S23.
And output it by appending it to the end of the text data in the file corresponding to the subject received in.

Then, as step S22, step S22
The data in the file to which the text data is output in step S21 or step S23 is processed into the format of the compiler used by the user, and is compiled to generate or update the difference program. To the command input state from the operator.

FIG. 6 is a flowchart showing the process of registering maintenance data in the server in step S4 of FIG. When the registration process is started, the operator first requests the operator to input the subject and the type of registration of the maintenance data to be registered in step S31, and receives them.

The type of registration received in step S31 is
If it is provisional registration (step S32, provisional registration), the operator requests and receives an input of the scheduled date of the maintenance work in step S33. Then, maintenance data to be registered together with the information is sent to the power distribution server via the network, and a registration request is made. Then, control goes to a process of step S37.

If the type of registration received in step S31 is formal registration (step S32, formal registration), then in step S35, the operator is requested to input the completion date of the maintenance work, and this is entered. Receive. And send these NO data along with the subject to the distribution server,
The main registration is requested, and the process proceeds to step S37.

Then, step S34 or step S2
The result received from the power distribution server in response to the registration request in step S6 is received (step S37), this is notified to the operator as step S38, and the registration processing is terminated, and step S1 in FIG.
To the command input state from the operator.

FIG. 7 is a flowchart showing processing performed by the power distribution server in response to a maintenance data registration request from a client device at each business office. First, in step S41, the power distribution server receives a maintenance data registration request from a client device installed in each business office via a network.

In response to this, the power distribution server processes the maintenance data sent together with the request or the maintenance data of the corresponding subject temporarily registered in its own database into the format of the compiler used by itself, and compiles it. (Step S4)
2).

Then, by executing the difference program, the maintenance data requested to be registered is developed into the base data (step S43). Then, as step S44, a logic check of the maintenance data is performed.
The logical check is to check for unrolling errors,
It is checked whether all necessary data, such as the line type of the wiring, the capacity of the switch, and the number of units in the section, has been input, and the direction of the switch.

If there is a problem as a result of the logic check (N in step S45), an error notification is sent to the client device which has issued the registration request in step S49, and the process ends. If there is no problem as a result of the logic check in step S44 (step S45, Y), the maintenance data is registered.

In the case where the registration of the maintenance data is formal registration (step S46, formal registration), step S43 is performed.
The data of the distribution system diagram in which the maintenance data has been developed is registered as new base data (step S47),
If it is temporary registration (step S46, temporary registration), the maintenance data is registered as temporary maintenance data in its own database (step S48). Then, in step S50, the registration of the maintenance data is performed on the client device that has issued the registration request, and the process is terminated.

FIG. 8 is a diagram showing a system environment of a power distribution server on which the maintenance system according to the present embodiment operates and a client device of each business office. As shown in FIG. 8, the information processing system includes a CPU 11, a main storage device 12, a hard disk device 13, an input / output device (I / O) 14 such as a display, a keyboard and a mouse, a network connection device 15 such as a modem, a disk, Medium reading device 16 for reading stored contents from a portable storage medium such as a tape
And these are connected to each other by a bus 17.

In the information processing system of FIG. 8, a magnetic tape, a floppy disk,
Reading out a program and data stored in a storage medium 18 such as a ROM and an MO, and downloading them to the main storage device 12 or the hard disk 13; Each process according to the present embodiment can be realized by software by the CPU 11 executing the program or data.

In this information processing system, application software may be exchanged using a storage medium 18 such as a floppy disk. Therefore, the present invention is not limited to the maintenance system, and may be configured as a computer-readable storage medium 18 for causing a computer to perform the functions of the above-described embodiments of the present invention when used by the computer. .

In this case, the “storage medium” includes, for example, FIG.
As shown in FIG. 3, the data is transmitted via a removable storage medium 26 such as a CD-ROM, a floppy disk (or an MO, a DVD, or a removable hard disk) or a removable storage medium 26 or a network line 23. A storage means (database or the like) 22 in an external device (a server or the like) to be performed, or a storage device (RAM or a hard disk or the like) 25 in a main body 24 of the information processing apparatus 21 is included. The program stored in the portable storage medium 26 or the storage means (database or the like) 22 is loaded into a memory (RAM or hard disk or the like) 25 in the main body 24 and executed.

In the embodiment of the present invention described above, the maintenance data is output in a text format.
Although it was a method of compiling with a power distribution server or client device that develops this, the present invention is not limited to this, and for example, data indicating an operation performed by an operator on maintenance data is output in a text format or a binary data format, and It is also possible to use an interpreter system in which a program on a power distribution server or a client device directly reproduces processing from data. In this case, there is no need to compile the maintenance data, and the interpreter program only calls the update routine based on the maintenance data to perform the processing. Therefore, the processing speed at the time of development is almost the same as that of the compile method. It is also possible to perform a debugging process using an editor.

In this embodiment, the maintenance system has a configuration in which the server and the client device of each office are connected by a network. However, the present invention is not limited to such a configuration. Instead, for example, the present invention can be applied to a maintenance system configured as a single system for each business office or a maintenance system having a plurality of client devices in one business office.

[0079]

According to the present invention, even if the order in which the maintenance data is expanded is changed, the maintenance data can be expanded without causing an expansion error due to abnormal link information. Even if another deployment error occurs, the device that caused the error can be clearly shown.

Further, when the difference program is executed to develop the maintenance data, a plurality of facilities are not set to the same facility number, and the facility maintenance at the border between the offices and the facilities near the two offices is not performed. Even data can be deployed without any problems.

Further, there are a plurality of types of devices for handling maintenance data, such as devices using different CPUs or OSs. Even if the maintenance data is transferred between different models, the maintenance data can be developed without any problem.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating maintenance data in the present embodiment.

FIG. 2 is a diagram showing a source program of a difference program.

FIG. 3 is a diagram illustrating an overall flow of a maintenance process according to the embodiment.

FIG. 4 is a flowchart illustrating a process performed by a client device.

FIG. 5 is a flowchart illustrating a maintenance process.

FIG. 6 is a flowchart showing a process of registering maintenance data in a power distribution server.

FIG. 7 is a flowchart illustrating a process performed by a power distribution server in response to a maintenance data registration request from a client device of each business office.

FIG. 8 is a diagram illustrating a system environment of a power distribution server or a client device on which a maintenance system operates.

FIG. 9 is a diagram illustrating an example of a storage medium.

FIG. 10 is a diagram illustrating maintenance data.

FIG. 11 is a diagram illustrating registration of data to wirings and switches.

FIG. 12 is a diagram illustrating a case where maintenance data of a subject A2 is expanded to base data without expanding maintenance data of a subject A1.

FIG. 13 is a diagram showing a configuration of a conventional distribution system monitoring system.

FIG. 14 is a diagram illustrating a case where a facility number is duplicated during deployment.

[Explanation of symbols]

SW0, SW1, SW2 switch line1, line2, line3, line4, l
ine5 wiring P0 telephone pole 11 CPU 12 main storage device 13 hard disk device 14 input / output device 15 network connection device 16 storage medium reading device 17 bus 18 storage medium

Claims (8)

[Claims] 1. A maintenance system in which a plurality of client devices are connected to a server via a network, wherein each of the client devices generates a distribution system diagram on a screen; An operation receiving unit for receiving an operation by an operator, an operation storage unit for sequentially storing the operation by the operator, a registration requesting unit for requesting the server as data indicating the operation stored in the operation storage unit as maintenance data, The server comprises: a registration unit for registering the maintenance data in a database; and performing a logical check of the maintenance data in response to a maintenance data registration request from the client device. Registration processing means for registering Maintenance system according to claim. 2. The maintenance system according to claim 1, further comprising a difference program generating unit that compiles the maintenance data and generates a difference program that reproduces the operation performed by the operator. 3. A client device constituting a maintenance system in a distribution system monitoring and control system, comprising: a screen generation unit that generates a distribution system diagram on a screen; and an operation receiving unit that receives an operation performed by an operator on the distribution system diagram. And an operation storage unit for sequentially storing operations by the operator, and a registration request unit for requesting registration of data indicating the operation stored in the operation storage unit as maintenance data. 4. A maintenance method in a distribution system monitoring and control system, comprising: generating a distribution system diagram on a screen, and updating the distribution system diagram corresponding to an operation performed by an operator on the distribution system diagram. And sequentially storing operations performed by the operator, and registering data indicating the stored operations as maintenance data. 5. The maintenance method according to claim 4, wherein the operation by the operator is stored as the update routine called in response to the operation. 6. The maintenance method according to claim 4, wherein the maintenance data is compiled, and a difference program for reproducing the operation by the operator is generated. 7. A distribution system diagram is generated on a screen of a computer, an update routine for updating the distribution system diagram corresponding to an operation performed by the operator on the distribution system diagram is called, and operations performed by the operator are sequentially stored in a memory. And a computer-readable storage medium storing a program for causing the computer to request that data indicating an operation stored in the memory be registered as maintenance data. 8. Receiving a maintenance data registration request, compiling the maintenance data having the registration request to generate a difference program, executing the generated difference program, and storing the maintenance data in a power distribution system diagram. Developed into base data, performed a logical check on the distribution system diagram, and stored a program for causing a computer to register the maintenance data with the registration request if there was no problem in the logical check. A storage medium readable by the computer.