JP2006040157A - Repair form management system and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To streamline repair work on distribution equipment or the like by managing on a system a repair form describing repairs on a failed part of the distribution equipment. <P>SOLUTION: A repair form management server 10 comprises a data reception part 50 for receiving data on equipment failure from a user terminal 30; a repair form database 12 for storing the received data as repair form data; a repair form inquiry part 52 for sending the repair form data in the repair form database 12 to the user terminal 30 in response to an inquiry request from the user terminal 30; a process management database 16 for storing process management information indicating an approval order and approval progress status about each repair form; an approval reception part 54 for extracting the repair form that the corresponding user should approve from the process management database 16 and sending it to the user terminal 30 so as to receive an approving operation in response to an approving request from the user terminal 30; and an approval recording part 56 for updating the process management information in the process management database 16 according to the received approving operation. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a system and method for managing a repair slip issued for repairing defects in power facilities in an electric power company or the like.

  An electric power company has an enormous number of power distribution facilities including utility poles and electric wires, and it is necessary to perform repair work when a defective part occurs in each power distribution facility. Conventionally, repair work of a defective part of a power distribution facility in an electric power company is performed in the following procedure, for example. That is, a patrol inspection is performed to check a defective part of the power distribution facility, and when a defective part is found, a person in charge of the patrol inspection writes down the details of the defect and notifies the internal operation department. When the operator in charge of the electric power company receives a notification of a defect from the inspection and inspection person in charge, it issues a repair slip that describes the details of the defect, and the operator in charge of the operation department determines the need for repair and issues a repair slip. approve. The approved repair slip is circulated to the design department, and a person in charge of the design department creates a design document based on the repair slip. The design document is approved by the person in charge of the design department, then circulated to the construction department, and repair work is performed based on the design document. It should be noted that there is no information that the present applicant has known about prior literature relating to such a system for managing a repair slip at the time of this application.

  As described above, the issue of the repair slip is performed by copying the content of the defect notified by the person in charge of operation from the person in charge of inspection and inspection on the slip, so that the business efficiency is poor. Moreover, since there are a huge number of power distribution facilities, the number of defects has risen to a considerable number, and a large number of repair slips are issued, so it takes a lot of time to issue repair slips. End up. In addition, since a repair slip is issued each time a failure of the distribution facility is discovered, the list of repair slips is poor, and it is difficult to manage the priority of which abnormality should be prioritized for repair. Furthermore, paper-based repair slips can be lost, and information related to repair slips is difficult to share, so there is a risk of double issuance. As described above, the work related to the repair of the power distribution equipment using the conventional repair slip is not always efficient.

  The present invention has been made in view of the above points, and by managing on the system a repair slip that describes the repair contents of a defective part such as a distribution facility, the repair operation of the distribution facility can be performed efficiently. The purpose is to do.

To achieve the above object, the present invention comprises a computer system connected to a user terminal via a network, and manages a repair slip for managing a defective portion of a distribution facility and a repair slip indicating the content of the failure. A system,
A data receiving unit that receives data indicating a defective portion of the power distribution facility and the content of the defect from the terminal of the user who has accessed;
A repair slip database for storing the data received by the data receiver as repair slip data;
A repair slip inquiry unit that transmits the repair slip data stored in the repair slip database to the user terminal in response to an inquiry request from the accessing user terminal;

The repair slip management system includes a process management database in which process management information indicating the approval order and the progress of approval is stored for each repair slip;
In response to an approval request from the accessing user's terminal, a repair slip to be approved by the user is extracted from the process management database and transmitted to the user's terminal, and the approval operation is performed from the user's terminal. An approval reception unit for receiving,
An approval recording unit that updates process management information stored in the process management database based on an approval operation received by the approval receiving unit may be further included.

  The repair slip data may be classified according to the type of the repair target device, and may include a data item corresponding to the type.

  ADVANTAGE OF THE INVENTION According to this invention, it becomes possible to perform the repair work of a power distribution equipment efficiently by managing the repair slip which described the repair content of defective parts, such as a power distribution equipment, on a system.

  Hereinafter, a repair slip management system according to an embodiment of the present invention will be described. In this embodiment, when a person in charge of inspection of distribution facilities of a power company finds a defect in the facility, the repair slip management system is issued on the system by accessing the repair slip management system from the mobile terminal. . The issued repair slip can be viewed by the person in charge of the operation department, the person in charge and / or person in charge of the construction design department, and the construction company, and the repair work is carried out after approval in each department according to the business flow. The

  FIG. 1 is an overall configuration diagram of a repair form management system according to an embodiment of the present invention. The repair slip management system of this embodiment includes a repair slip management server 10. The repair slip management server 10 is configured by a computer system including a CPU, a memory, a storage device, a communication interface, and the like. As shown in FIG. 1, the repair slip database 12, the image information database 14, the process management database 16, and the use Each person information database 18 is provided.

  In addition, as shown in FIG. 1, the repair slip management server 10 includes mobile terminals 20 such as mobile phones and PDAs possessed by a person in charge of inspection of distribution facilities, and departments such as an operation department, a management department, and a design department. The computer terminal 22 operated by the person in charge or the person in charge is connected via a wireless or wired network. When the inspection inspection person finds a defective part during inspection inspection of the distribution facilities such as the power pole and the electric wire, the inspection person in charge accesses the repair form management server 10 from the portable terminal 20 possessed, and creates a repair form by inputting the contents of the defect. be able to. In addition, when the person in charge of the operation department grasps the defective part of the distribution facility by, for example, a report from a general user, similarly, it accesses the repair slip management server 10 from the computer terminal 22 and creates a repair slip. be able to. The repair slip data created in this way is stored in the repair slip database 12. Further, the manager of the operation department, the person in charge of the management department, the design department, and the construction department or the person in charge of the management department accesses the repair form management server 10 from the computer terminal 22 to view and approve the repair table. Can do. In the present application, the person in charge and the person responsible for creating, viewing, and approving the repair slip by accessing the repair slip management server 10 as described above are collectively referred to as a user, and the portable terminal 20 and the computer The terminal 22 is generically called a user terminal 30.

  The repair slip management server 10 is connected to a ground data management system 40 for managing the ground resistance of each distribution facility and a design management system 42 for managing a construction design work based on the repair slip, as will be described later. The repair slip management server 10 can operate in conjunction with these systems 40 and 42.

  The repair slip database 12 stores data representing each created repair slip (hereinafter referred to as repair slip data). In the present embodiment, the repair slips are managed by being classified into types such as “general”, “grounding”, “protection pipe”, and “wood pole”.

  2 to 5 show examples of the configuration of repair slip data stored in the repair slip database 12 for the types “general”, “grounding”, “protection pipe”, and “wood pole”, respectively. As shown in FIGS. 2 to 5, the repair slip data stored in the repair slip database 12 includes the business site code, repair slip type code, issuer code, issue date, serial number, importance, and urgency Data items common to all types and data items set for each type are included. Here, the serial number is a number for discriminating repair sheets having the same issue place code, repair form type code, issuer code, and issue date. That is, each repair slip can be identified by the issuer code, the date of issue, and the serial number, and the number in which these are arranged is used as the repair slip number.

  The image information database 14 stores images such as a photograph of a defective part and a map in association with each repair slip. FIG. 6 shows an example of the structure of data recorded in the image information database 14. As shown in the figure, the image information database 14 records an image ID, an image file name, and the like in association with the repair slip number (issuer code, issue date, serial number) of each repair slip. Yes. In some cases, a plurality of image data is registered for one repair slip. In that case, a plurality of image IDs and image file names corresponding to the respective image data are recorded. Further, the image data itself is separately registered in an image database (not shown).

  In the process management database 16, data on the workflow for each of the created repair slips until the construction is ordered after the approval of the operation department and the design department is recorded. FIG. 7 shows a configuration example of data recorded in the process management database 16. As shown in the figure, in the process management database 16, in relation to the repair slip number of each repair slip, the reception date / recipient / approver / approval date of the repair slip in the operation department is rejected. Rejector / Rejection date / Reason for rejection, Design department designer / Design document number / Design completion date / Design approval date / Design approver / Design document delivery date / issuer, Construction completion date, work manager, construction completion approval Date, construction completion approver, etc. are recorded. Among these, items related to design are received from the design management system 42 connected to the present system and stored in the process management database 16.

  FIG. 8 shows a configuration example of data stored in the user information database 18. As shown in the figure, the user information database 18 includes a name, a user code, a password, a department code, a business office code, and a job position code (for example, responsible person, deputy manager, Etc.) are recorded.

  FIG. 9 is a functional block diagram showing main functional units of the repair slip management server 10. As shown in FIG. 1, the repair slip management server 10 includes functional units such as a data receiving unit 50, a repair slip inquiry unit 52, an approval receiving unit 54, and an approval recording unit 56. These functional units are realized by a computer constituting the repair slip management server 10 executing a program.

  The data receiving unit 50 receives data representing a defective portion of the power distribution facility and the content of the defect from the user terminal 30 that has accessed the repair slip management server 10. The data received by the data receiving unit 50 is stored in the repair slip database 12 as repair slip data.

  The repair slip inquiry unit 52 transmits the repair slip data stored in the repair slip database 12 to the user terminal 30 in response to an inquiry request from the user terminal 30 that has accessed the repair slip management server 10.

  The approval receiving unit 54 extracts a repair slip to be approved by the user from the process management database 16 in response to an approval request from the user terminal 30 and transmits it to the user's terminal. Accept the approval operation. The approval recording unit 56 updates the process management information stored in the process management database 16 based on the approval operation received by the approval receiving unit 54.

  Hereinafter, the content of the process in this embodiment is demonstrated. First, processing when issuing a repair slip or making an inquiry from the user terminal 30 will be described.

  FIG. 10 shows an overview of the flow of processing when the repair slip management server 10 is accessed from the user terminal 30 to issue or inquire a repair slip in this embodiment.

  As shown in the figure, during inspection inspections, inspection inspection personnel who are trying to find defective parts and issue repair slips, or operations that try to issue repair slips after receiving reports of defective parts from general users The department person in charge accesses the repair slip management server 10 from the user terminal 30 (S100). In response to this, the repair slip management server 10 transmits a login screen including a user code and password input field to the user terminal (S102). The user code and password entered on this login screen are transmitted to the repair slip management server 10 (S104), and the repair slip management server 10 collates them with the user code and password stored in the user information database 18. Thus, user authentication is performed (S106). If the authentication is successful, login is permitted and the screen data of the main menu screen is transmitted to the user terminal 30 (S108). The main menu screen includes a repair slip creation / inquiry menu and a repair slip approval menu. When the repair form creation / inquiry menu is selected on this screen (S110), the repair form management server 10 transmits a repair table list screen as shown in FIG. 11 to the user terminal 30 (S112).

  As shown in FIG. 11, the repair slip list screen includes a search condition input field 500, a search button 502, a list display field 504, a creation button 506, a repair slip detail button 508, and the like. In the search condition input field 500, search conditions for searching for a repair ticket that has already been created can be set for each item such as type, track name, importance, and degree of urgency. When the search button 502 is clicked (S114), the search condition set in the search condition input field 500 is transmitted to the repair slip management server 10 (S116). The repair slip management server 10 refers to the repair slip database 12 and searches for the repair slip data corresponding to the search condition (S118), transmits it to the user terminal 30 (S120), and displays it in the list display column 504.

  When the repair slip detail button 508 is clicked in a state where any repair slip is selected in the list display field 504 (S122), an inquiry request for the repair slip is transmitted to the repair slip management server 10 ( S123). When the repair slip inquiry unit 52 of the repair slip management server 10 receives this trade request, it reads the requested repair slip data from the repair slip database 12 and generates a repair slip screen for displaying it (S124). It transmits to the terminal 30 (S126).

  On the other hand, when creating a new repair slip, the person in charge designates the type of repair slip to be created in the type field of the search condition input field 500 and then clicks the create button 506 (S128). When the creation button 506 is clicked, a request for creating a specified type of repair slip is transmitted to the repair slip management server 10 (S129). In response to this, the repair slip management server 10 generates a repair slip screen for creating a repair slip of the corresponding repair slip type (S130) and transmits it to the user terminal 30 (S131).

  FIG. 12 shows an example of a repair slip screen for the repair slip type “general”. 12 and the following repair slip screens have the same appearance as the repair slip screen transmitted in S126. That is, the repair slip screen in the case of the repair slip inquiry is transmitted to the user terminal 30 with the corresponding repair slip data displayed in each column, while the repair slip screen in the case of creating the repair slip is displayed in each column. Is transmitted to the user terminal 30 in a blank state.

  As shown in FIG. 12, the repair slip screen includes input fields for various items. Of these, for a work category, by clicking a “work category” button 510, a sub-window 520 opens as shown in FIG. 13, and the work category can be selected from the options. As for the product name standard of the equipment to be repaired, by clicking the “input” button 512, as shown in FIG. 14, a sub-window 522 is opened, and the product name standard, installation quantity, reuse quantity, removal quantity are displayed. You can enter. Also, by clicking a “track name search” button 514, a track name search window is opened, and a track name can be searched and input on this screen. The “image” button 516 functions in the case of a screen for inquiring a repair slip. When this button 516 is clicked, the repair slip management server 10 displays image information registered for the repair slip in the image information database 14. And a screen for displaying them as a list is transmitted to the user terminal 30. The registration of the image information is performed, for example, by transmitting the repair slip number and the photo image from the portable terminal 20 to the repair slip management server 10 and saving the photo image with a file name in the repair slip management server 10. The repair slip number and the image file name are associated with each other and stored in the image information database 14.

  FIG. 15 shows an example of a repair slip screen for the repair slip type “grounding”. A repair slip for the type “grounding” is created when a grounding failure point is found as a result of grounding resistance measurement performed in a timely manner. As shown in FIG. 15, for the repair slip type “grounding”, a list area 530 for displaying a list of registered repair slip data of the type “grounding” and an “input” button 532 are provided. When the “input” button 532 is clicked, a detailed input window 534 as shown in FIG. 16 is opened, and detailed items such as a device type, a support type, and an installation work type can be input on this screen. As described above, the repair slip management server 10 is connected to the ground data management system 40 for managing the ground resistance measurement result, and the ground resistance of the corresponding line from the ground data management system 40 is defective. Data can be imported and automatically entered in the detailed input window.

  FIG. 17 shows an example of a repair slip screen for the repair slip type “protection pipe”. The protective pipe is attached so as to cover the electric wire as a mark so that an operator does not touch the electric wire accidentally when the power distribution facility is constructed. Since it is easy to leave the protective pipe attached after the work is completed, a repair slip for the “protective pipe” is created when the protective pipe is attached, and the installation state of the protective pipe is managed.

  As shown in FIG. 17, the repair slip screen for “protection pipe” includes operation buttons such as a “reason for trouble” button 540, an “installation quantity input” button 542, and an “other information” button 544. When the “reason for trouble” button 540 is clicked, a window 546 is opened as shown in FIG. 18, and the reason for the trouble can be selected and input. When the “attached quantity input” button 542 is clicked, a window 548 is opened as shown in FIG. 19, and the attached quantity can be entered for each type of protective pipe. When the “other information” button 544 is clicked, a window 550 is opened as shown in FIG. 20, and the installation information of the protective pipe installation requester, the removal completion date of the protective pipe, and the removal information of the understanding person, etc. Can be entered.

  FIG. 21 shows an example of a repair slip screen for the repair slip type “wood pole”. As shown in the figure, the repair slip screen includes an “input” button 560. When this button is clicked, a window 562 opens as shown in FIG. Detailed information such as equipment category and type can be entered.

  When input is made in the input field on the various repair table creation screens as described above and the “Register” button 518 included in each button is clicked (S132), the input data is transmitted to the repair slip management server 10 ( S134), and is received by the data receiver 50. The received data is stored in the repair slip database 12 as repair slip data (S136).

  In addition, the prepared repair slip is approved through a predetermined circulation route, and repair work based on the repair slip is performed. Here, the approval operation for the repair slip will be described.

  FIG. 23 shows an overview of the flow of processing related to the repair slip approval operation. As shown in the figure, when the repair form approval menu is selected on the main menu screen (S150), an approval request is transmitted from the user terminal 30 to the repair form management server 10 (S151). Upon receiving this approval request, the approval receiving unit 54 of the repair slip management server 10 generates a repair slip approval target list screen illustrated in FIG. 24 (S152) and transmits it to the user terminal 30 (S154).

  As shown in FIG. 24, the repair slip approval target list screen displays a list of repair slips waiting for approval by the logged-in user. That is, the approval receiving unit 54 identifies the user from the user ID input at the time of login, refers to the process management database 16, and refers to the repair slip that is waiting for approval by the user, that is, in the workflow. A repair slip that has been approved by the approver immediately before the user is extracted and displayed on the repair slip approval target list screen. For example, in the example of the process management database 16 in FIG. 7 described above, when the user is a section manager of the operation department, a repair slip recorded until the approval date by the deputy head is extracted.

  When the “repair sheet inquiry” button 570 is clicked in a state where any one of the repair sheets is selected on the repair sheet approval object list screen (S156), the approval reception unit 54 of the repair sheet management server 10 is selected. The repair slip data is read from the repair slip database 12 (S158) and transmitted to the user terminal 30 (S160).

  In addition, in a state where any repair slip is selected on the repair slip approval target list screen, the “direct construction approval” button 572, the “contract construction approval” button 574, or the “emergency construction approval” button 576 is clicked. (S162), the approval recording unit 56 of the repair slip management server 10 records the name of the user as the approver of the selected repair slip in the process management database 16 and records the approval date (S164). ). When the “denial” button 578 is clicked, an input screen for inputting the reason for rejection is transmitted from the repair form management server 10 to the user terminal 30. It is recorded in the process management database 16 together with the date.

  Further, when the “change route” button 578 is clicked in a state where any repair slip is selected on the repair slip approval target list screen (S166), the repair slip management server 10 exemplifies FIG. Such a circulation route setting screen is generated (S168) and transmitted to the user terminal 30 (S170). As shown in FIG. 25, in the circulation route setting screen, the circulation route recorded in the process management database 16 is displayed as a block 600 for each process, and the approver and the approval date are recorded for each process. The approver and approval date are displayed in the block. In the example of FIG. 25, it is shown that the process has progressed to the reception of the manager in charge (Taro Nakaden, 2004/3/16). When the “→” button 602 between process blocks is clicked on the circulation route setting screen, a new process can be added, and any process is selected and the “delete” button 604 is clicked. Then, the process can be deleted. When the process addition or deletion operation is performed and the “Register” button 606 is clicked (S172), the repair slip management server 10 updates the circulation route recorded in the process management database 16 accordingly. (S174).

  As described above, a circulation route is set for each repair slip, and an approval operation is performed according to the circulation route. When final approval in the operation department is completed, the repair slip data is passed to the design department. After that, the design department prepares and approves design documents, and performs process management such as construction instructions to the construction department. Done. At that time, the repair slip number is used as a key and associated with the repair slip that is the basis of the design, so that the process management data in the design department can be taken into the process management database 16 as described above. .

  As described above, according to the system of the present embodiment, the inspection person in charge of inspection can access the repair form management server 10 from the user terminal 30 such as the portable terminal 20 and create the repair form online. Thus, the work efficiency of issuing a repair slip is significantly improved compared to copying the inspection inspection result on the repair slip. Further, the created repair slip is managed as electronic data on the server, and related parties can view the repair slip from each user terminal 30. For this reason, it becomes possible to share repair slip data between users, and it is possible to prevent inefficient situations such as double issuance of repair slips.

  In addition, since the issued repair slip can be searched and displayed as appropriate according to type, importance, urgency, region, etc., it is easy to give priority to repairs, for example, inspection inspection It is also possible for the person in charge to inquire about a repair slip for the vicinity of the inspection inspection area, and to check the defect status or perform repairs.

  In addition, a repair slip circulation route can be set, and the repair slip can be circulated to the design department after receiving approval through a route according to the circulation route. For this reason, as in the case of using a paper-based repair slip, it is possible to adapt to repair work in a form in line with the in-house management system.

1 is an overall configuration diagram of a repair slip management system according to an embodiment of the present invention. It is a figure which shows the data item of the repair slip data stored in the repair slip database about the repair slip classification “general”. It is a figure which shows the structural example of the repair slip data stored in the repair slip database about the repair slip classification “grounding”. It is a figure which shows the structural example of the repair slip data stored in the repair slip database about repair slip classification "protection pipe". It is a figure which shows the structural example of the repair slip data stored in the repair slip database about the repair slip classification “wood pole”. It is a figure which shows the data structural example of an image information database. It is a figure which shows the example of a data structure of a process management database. It is a figure which shows the example of a data structure of a user information database. It is a functional block diagram which shows the main function parts of a repair slip management server. It is a figure which shows the outline | summary of the flow of a process in the case of accessing a repair slip management server from a user terminal in this embodiment, and issuing a repair slip or inquiring. It is a figure which shows an example of a repair slip list screen. FIG. 10 is a diagram (part 1) illustrating an example of a repair slip screen for a repair slip type “general”; FIG. 10 is a second diagram illustrating an example of a repair slip screen for a repair slip type “general”. FIG. 10 is a third diagram illustrating an example of a repair slip screen for a repair slip type “general”; FIG. 10 is a diagram (part 1) illustrating an example of a repair slip screen for a repair slip type “grounding”; FIG. 10 is a second diagram illustrating an example of a repair slip screen for a repair slip type “grounding”; FIG. 10 is a diagram (part 1) illustrating an example of a repair slip screen for a repair slip type “protection pipe”; It is FIG. (2) which shows an example of the repair slip screen about repair slip classification “protection pipe”. FIG. 11 is a diagram (part 3) illustrating an example of a repair slip screen for a repair slip type “protection pipe”; It is FIG. (4) which shows an example of the repair slip screen about repair slip classification "protection pipe". FIG. 10 is a diagram (part 1) illustrating an example of a repair slip screen for a repair slip type “wood pole”; FIG. 12 is a second diagram illustrating an example of a repair slip screen for a repair slip type “wood pole”; It is a figure which shows the outline | summary of the flow of the process regarding approval operation of a repair slip. It is a figure which shows an example of a repair slip approval object list screen. It is a figure which shows an example of a circulation route setting screen.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Repair form management server 12 Repair form database 14 Image information database 16 Process management database 18 User information database 20 Mobile terminal 22 Computer terminal 30 User terminal 40 Grounding data management system 42 Design management system 50 Data receiving part 52 Repair form reference part 54 Approval reception part 56 Approval recording part

Claims (5)

A repair slip management system for managing a repair slip indicating a defective portion of a power distribution facility and the content of the failure, comprising a computer system connected to a user terminal via a network,
A data receiving unit that receives data indicating a defective portion of the power distribution facility and the content of the defect from the terminal of the user who has accessed;
A repair slip database for storing the data received by the data receiver as repair slip data;
A repair slip comprising a repair slip reference unit that transmits repair slip data stored in the repair slip database to the user's terminal in response to an inquiry request from the accessing user's terminal. Management system. In the repair slip management system according to claim 1,
A process management database storing process management information representing the approval order and the progress of approval for each repair slip;
In response to an approval request from the accessing user's terminal, a repair slip to be approved by the user is extracted from the process management database and transmitted to the user's terminal, and the approval operation is performed from the user's terminal. An approval reception unit for receiving,
The repair slip management system according to claim 1, further comprising: an approval recording unit that updates process management information stored in the process management database based on an approval operation received by the approval receiving unit.   3. The repair slip management system according to claim 1, wherein the repair slip data is classified according to a type of a repair target device and includes a data item corresponding to the type. A method for managing a defective part of a power distribution facility and a repair slip indicating the content of the defect by a computer system connected to a user terminal via a network,
The computer system receives from a terminal of a user who has accessed data representing a defective part of a power distribution facility and details of the defect;
The computer system storing the received data in a repair slip database as repair slip data;
The computer system comprises a step of transmitting repair slip data stored in the repair slip database to the user terminal in response to an inquiry request from the accessing user terminal. Repair slip management method. In the repair slip management method according to claim 4,
In response to an approval request from the user's terminal that the computer has accessed, the user approves from the process management database in which process management information indicating the approval order and the progress of approval for each repair slip is stored. Extracting a repair slip to be transmitted and transmitting it to the user's terminal, and receiving an approval operation from the user's terminal;
Updating the process management information stored in the process management database based on an approval operation received by the approval receiving unit.