JP2003178149A - Maintenance management system for plant and maintenance method for plant - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system for detecting troubles in a plant with reliability and for immediately reporting to the corporation in charge for implementation of appropriate measures. <P>SOLUTION: Documents relating to plants and control systems are arranged in a maintenance management unit 101 on a network, and plant operating conditions and system error occurrences are also registered therein. When an error occurs in the plant, information is automatically generated on the pending problem and made to be looked at by corporations on the net, such as a plant managing corporation A and system development and maintenance management corporations B, C. The corporation A witnesses the responses of the corporations B, C on the unit 101. <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a maintenance management system for a plant control system and its service.

[0002]

2. Description of the Related Art In conventional plant monitoring and control systems,
The vendor who developed the system created the operation manual and maintenance manual and delivered them to the plant operating company, that is, the user. The user operated the supervisory control system while viewing those manuals to control the plant. At that time, if a trouble occurs in the plant that cannot be dealt with manually, the user will contact the vendor,
I was instructing me to investigate the cause of the trouble and take countermeasures.

[0003]

However, in the case of a problem that cannot be dealt with by the user in the above-mentioned conventional technique, it took time for the trader to receive a report from the user and investigate the cause and take a countermeasure. In addition, since the user must constantly monitor and manage the pending matter, the human burden is large.

In view of the above problems of the prior art, an object of the present invention is to provide a plant maintenance method and a maintenance management system, which act on behalf of the user's manual management and management of pending matters.

[0005]

SUMMARY OF THE INVENTION The present invention for achieving the above object includes a facility database of facilities used in a plant control system, and in a system for inputting operation information of a plant for maintenance management, An error code related table that corresponds error codes and equipment names for each abnormality, and a company name that generates a pending item including the pending content and date and time of occurrence in response to the error code when a plant error occurs, and is also in charge of the pending measures. And a pending generation registration function that can register the corresponding state.

Further, a document for storing the specifications and operation manual of the equipment as electronic information is provided, and the equipment database stores the operating status of each equipment name and location information for enabling reference of related documents, It is characterized in that an operation status registration function for indicating the operation status of the plant is provided by referring to the equipment database.

Further, it is characterized in that a maintenance procedure manual or its location information related to each error of the error code related table is stored and can be presented to the outside.

Further, the plant maintenance method of the present invention connects the maintenance management device for monitoring the operation information of the plant, the terminal of the plant operating company, and the terminal of the plant development / maintenance company by a network to perform the maintenance management. The device monitors the operating condition of each facility of the plant, generates pending information when a plant abnormality occurs and notifies the operating company, the operating company presents the pending information to the development / maintenance company, and the abnormality The feature is that the company that takes improvement measures responds to that fact.

Further, the maintenance management device charges at least the use of the operating company.

According to the present invention, the information of the plant control system is managed as the information on the network by the maintenance management device, so that the system user and the system developer / maintainer can always refer to the latest information. Further, since the information generated in the plant is associated with the manual, maintenance document, and design document to store the information, the necessary information can be easily retrieved.

Further, it is possible to generate a pending item in accordance with the occurrence of a trouble in the plant, determine a responsible company, and manage the pending item as information on the network.

[0012]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described in detail below with reference to the drawings. FIG. 1 shows the configuration of a plant maintenance management system according to an embodiment of the present invention. The maintenance management system for plant equipment according to the present invention is arranged in a service center such as iDC and provides services to users.

The plant equipment maintenance management apparatus 101 includes equipment data 102 including operation status and pending information data 10.
3. It holds data of related information 104, an operation / operation manual 105 managed in a hierarchical structure in a representation format such as a document or HTML, and design information 106 such as similar specifications and drawings.

The maintenance management apparatus 101 also has a dedicated line 10 for fetching information from the plant control system 107.
8. Connected to the communication network 109 for connecting to the system user. The communication network 109 is the Internet / Intranet, and the terminal 110 of the plant operating company (Company A).
And terminals 111 and 112 of the system development / maintenance companies (Company B and C). Here, the plant operating company 110 is the system user of this system, and normally,
Part of the company in charge of system development and maintenance (Company B or C)
Manages and operates this system and collects usage fees from system users. However, the management and operation of this system may be performed by a third party other than the above. Further, the charge may be collected for all clients who use this system.

FIG. 2 is a block diagram of a maintenance management device for plant equipment. The maintenance management device 101 has the following functions in addition to the information and database described in FIG. It has an internet / intranet connection function 201 for managing connection to the internet / intranet and distribution of data to clients (including data for displaying a screen). Also, a user authentication device 202 for identifying a system user, a user management database 203 in which available users are registered, and display information generation for collecting information from various databases and generating information to be displayed on the client. It has a function 204. It also has a document management / data correction function 205 for registering / correcting the data of documents registered in each database in accordance with a request from a system user. In addition, it receives information from the control system 107 to generate a pending matter based on the operating status and trouble, and a pending information database 1
It has an operation status / problem generation registration function 206 stored in 03.

Further, the related information 104 is the equipment related table 501 and the equipment and document related table 60.
1. An error code association table 701. The user mentioned above refers to all clients that use this system, and includes system users and traders.

FIG. 3 shows the structure of the user management database. The user management database 203 is a user name 20
31, a user ID 2032 used for authentication, and a password 2033 thereof are managed.

FIG. 4 shows the structure of the equipment database. The equipment database 102 is a list 10 of equipment to be controlled.
21 and a document location 1022 indicating specifications such as the structure and characteristics of the equipment (the document is held in the hierarchical structure of the design information 105). It also has information on the operation history of the equipment such as the date 1023 when the equipment is used and the expiration date 1024. Further, it also holds an operation status 405 indicating the current operation status (normal / abnormal) of the equipment.

The related information 104 includes equipment relation 501, equipment / document relation 601, and error code relation 70.
It consists of 1.

FIG. 5 shows the structure of the equipment table. The facility database 102 holds a facility data relation table 501 indicating the relation between facilities. This table is
The vertical axis 502 and the horizontal axis 503 are lined up with a list of facilities to be controlled, and a cross mark 5 is placed at the intersection of the vertical axis 502 and the horizontal axis 503.
When there is 04, it indicates that the equipment on the vertical axis and the equipment on the horizontal axis are related (affected). Facility data related table 501
Shows the relation of equipment in a matrix format, but may show in a list format having a pair of related equipment.

FIG. 6 shows the structure of a relation table of equipment and documents. This table 601 shows equipment and documents related to the equipment. A vertical axis (column) has a list 602 of facilities to be controlled, and a horizontal axis (row) has a list 603 of documents held (registered) by the maintenance management apparatus 101. A circle 604 at the intersection of the matrix indicates that the equipment on the horizontal axis is associated with the document on the vertical axis. By having this relation table 601, the relation between the equipment and the document can be immediately searched. However, it may be a means for searching all documents and extracting related documents.

FIG. 7 shows the structure of the error code relation table of the control system. This related table 701 is used for the control system 107 when a trouble occurs in the plant.
Error code 7 from the maintenance management device 101
02, a list 703 of equipment to be controlled, and a link 704 to a maintenance procedure manual on which a handling procedure for each error is applied.
The responsible company 705 corresponding to the error code is associated. In this relation table 701, the circle mark 70
If there is 5, the error code indicates the associated equipment.

FIG. 8 shows the structure of the pending information database. The database 103 has a serial number (N
o) 1031, pending title 1 that briefly describes the pending content
032, the pending content 1033 which specifically shows the content of the pending issue,
From the occurrence date and time 1034 indicating the date and time when the problem was generated, the responsible company 1035 indicating the company in charge of dealing with the trouble, the corresponding status 1036 indicating the response status of each responsible company, and the related error 1038 for entering the error number corresponding to the trouble. Composed.

The data used in this system are defined above. Next, the operation of this system will be described, including how these data are provided to the user who uses this system.

When the user accesses the maintenance management apparatus 101 from the terminal through the Internet / Intranet 109, the user input is the user management database 203.
Compared with the contents of, the system can be used by legitimate users. Maintenance management device 101 is database 2
The range that the user can refer to and the contents that can be operated are limited by the access range and access authority information of 03.

FIG. 9 shows an example of the monitoring screen of the control system. This screen is usually monitored by the system user. The monitoring screen 801 of the control system is the operation menu 8
There is a display switching menu 806 for switching the screen to 02 and an end menu 807 for ending the system. A structure display screen 803 showing the hierarchical structure of the plant equipment, a schematic display screen 804 showing the outline operation of the selected equipment, and a detailed display screen 805 showing the details of the equipment are displayed on the screen divided into three.

On the structure display screen 803, a tree structure of equipment is displayed based on the information of the equipment list 1021 of the control system. The outline display screen 804 displays a part of the information on the equipment selected from the tree structure. On this screen,
You can grasp the general condition of the selected equipment. Detailed display screen 80
The detailed information of the selected equipment is displayed at 5, and the information of the equipment list 1021 and the document selected from the equipment / document relation table 601 with the equipment as a key are displayed. By selecting the title of this document, the document can be displayed on the screen and referred to.

FIG. 10 is a monitor screen of the control system based on the error code. For example, by operating the display switching menu 806 while the monitoring screen of FIG. 9 is displayed, the maintenance management apparatus 101 is switched to the monitoring screen of FIG. Switch and display.

The difference from FIG. 9 lies in the structure display screen 901. The screen 901 retrieves an error code and its associated equipment from the error code-equipment related table 701 and displays them as a tree structure. The outline display 902 is a screen 90.
The operation status of the equipment related to the error code selected in 1 is displayed. At that time, the error code related table 70
Search 1 for the error code and search for the equipment. Similar to the screen of FIG. 9, the detailed display screen 903 displays the specifications and related materials of the corresponding equipment from the equipment database 102 and the equipment / document related table 601. Further, the maintenance procedure manual for the error code is retrieved from the error code relation table 701 and highlighted.

According to FIGS. 9 and 10, since a document such as an operation manual, design information, and maintenance procedure manual can be referred to through the location information, the user can easily retrieve necessary information.

Next, generation of pending information when a trouble occurs in the plant, and system user / system development /
Explain the correspondence and information flow of the maintenance company (contractor).

FIG. 11 is a flow chart showing the flow of pending issues when a trouble occurs. The maintenance management apparatus 101 receives a notification of occurrence of a trouble from the plant and generates a pending item (1101). For the pending item, the number in FIG. 8 is automatically numbered and the date and time of occurrence is entered. When the responsible company 705 is described in the error code related table 701, that company is designated as the responsible company 1035.

The maintenance staff of the plant operating company 110 (Company A) confirms the content of the automatically generated pending information, adds / corrects (1102) necessary information, and the system development / maintenance company, Company B, Notification is made via the C company network 109. Each company that receives this notice confirms the contents (11
03, 1104) and consider the correspondence.

The portion surrounded by the dotted frame 1105 shown in the figure is
The flow is shown when Company C is not in charge of this concern. The company C confirms the status of the trouble via the maintenance management device 101 (1106), and when it judges that this pending item is not in charge of its own company, it reports the corresponding state of the company C as not in charge (1107). Company A confirms the corresponding status via the maintenance management device 101 (1108).

The portion surrounded by the dotted line frame 1109 in the figure is B
The flow is shown when the company is in charge of this pending item. B
The company confirms the status of the trouble via the maintenance management device 101 (1110), and when the pending item is determined to be the company's responsibility, the company B's response status is reported as “charge” (11).
11). The company A confirms the report (1112) and gives an instruction for the corresponding work. Company B carries out plant recovery / improvement work and reports the work (1113). When the measures are completed, the pending response status is reported as “Company C: Completed”. The company A confirms the correspondence via the maintenance management device 101 (1114). In this case, the charge is the maintenance management device 1
01 may be performed only for company A.

In the above, the pending items are notified from the plant operating company (Company A) to the development / maintenance companies (Company B and C). However, when the maintenance item is generated by the maintenance management device 101, the company in charge may be immediately notified if the company in charge is already determined. Further, when the person in charge is undecided, it may be notified to all the related businesses. In this way, each company C may grasp the occurrence of a trouble on a common screen, and may instruct the company in charge of the trouble to perform the work. All users are charged for this method.

FIG. 12 is an example of a screen showing a list of pending matters. Display switching 806 is performed on the monitoring screen of FIG. 9 or FIG. 10, and a list screen of pending matters is displayed based on the pending information database 103. A screen area 1201 displays a list of pending issues, and a screen area 1202 displays detailed information of pending issues selected from the list.

FIG. 13 shows a list screen of pending matters by correspondence state. The response status 1036 to the pending status includes undecided, internal consideration, decision, competition, under consideration, and completed. On this screen, the pending issues are displayed separately for each response status (1301), and the details of the pending issues selected there are displayed in detail. From this screen, Company A can surely grasp the state of each pending issue.

In FIGS. 12 and 13, all the pending issues are displayed as screens monitored by the customer maintenance staff. But,
It is also possible to prepare a screen for displaying only the pending matters related to each of the B company and the C company, and to provide only the corresponding screen to the B company and the C company. Further, although the pending issue is displayed as the pending issue + No, the pending issue title may be displayed.

[0040]

According to the present invention, there is an effect that a matter of concern indicating a trouble of a plant or a control system can be easily managed. Further, according to this system, the maintenance management work of the plant operating company can be performed on behalf of the plant, and when a trouble occurs, the contractor can be instructed promptly to deal with the maintenance work.

[Brief description of drawings]

FIG. 1 is a configuration diagram of a plant equipment maintenance management system according to an embodiment of the present invention.

FIG. 2 is a block diagram showing functions of a maintenance management device.

FIG. 3 is a configuration diagram of a user management database.

FIG. 4 is a configuration diagram of a facility database.

FIG. 5 is a configuration diagram of a facility data related table.

FIG. 6 is a configuration diagram of an equipment / document related table.

FIG. 7 is a configuration diagram of an error code related table.

FIG. 8 is a configuration diagram of a pending information database.

FIG. 9 is an exemplary view of a monitoring screen for grasping the status of equipment.

FIG. 10 is a view showing an example of a monitoring screen for grasping the status of equipment from error codes.

FIG. 11 is a flow chart showing generation of pending information and a flow between companies.

FIG. 12 is an exemplary view of a screen showing a list of pending information.

FIG. 13 is an exemplary view of a screen showing a list of pending information by status.

[Explanation of symbols]

101 ... Maintenance management device, 102 ... Facility database, 1
03 ... pending information database, 104 ... related information database, 105 ... operation / operation manual, 106 ... design information, 107 ... control system, 108 ... dedicated line, 109
... Internet / Intranet, 110 ... System user terminal, 111, 112 ... System development / maintenance company terminal, 201 ... Internet / Intranet connection function, 202 ... User authentication function, 203 ... User management database, 204 ... Display information generation Function, 205
... Document management / data correction function, 206 ... Operating status / problem generation / registration function, 501 ... Equipment related table,
601 ... Equipment / document related table, 701 ... Error code related table.

Continued front page    (72) Inventor Izumi Furuuchi             5-2-1 Omika-cho, Hitachi City, Ibaraki Prefecture             Information Control Systems Division, Hitachi, Ltd.             Within (72) Inventor Takashi Iijima             5-2-1 Omika-cho, Hitachi City, Ibaraki Prefecture             Information Control Systems Division, Hitachi, Ltd.             Within (72) Inventor Keisuke Toji             5-2-1 Omika-cho, Hitachi City, Ibaraki Prefecture             Information Control Systems Division, Hitachi, Ltd.             Within F-term (reference) 5H223 AA01 BB01 DD03 DD07 DD09                       EE06

Claims (5)

[Claims] 1. A system comprising an equipment database of equipment used in a plant control system and performing maintenance management by inputting operation information of a plant, wherein an error corresponding to an error code for each abnormality of the plant and an equipment name A code-related table and a problem generation / registration function that can generate a problem item including the content of concern and date and time of occurrence in response to the error code when a plant error occurs, and can register the name of the company in charge of the problem countermeasure and its corresponding state. A plant maintenance management system characterized by the provision of. 2. The document according to claim 1, wherein a document for storing a specification sheet and an operation manual of the facility is provided as electronic information, and the facility database makes it possible to refer to an operating status of each facility name and a related document. A maintenance management system for a plant, which is provided with an operation status registration function for storing location information and referring to the facility database to indicate an operation status of the plant. 3. The maintenance management system for a plant according to claim 1, wherein a maintenance procedure manual or its location related to each error of the error code related table is stored and can be presented to the outside. . 4. A method for maintaining a plant by connecting a maintenance management device for monitoring plant operation information to each terminal of a plant operating company and a plant development / maintenance company by a network, wherein the maintenance management device is a plant. The operating status of each facility is monitored, and when an abnormality occurs in the plant, the pending information is generated and notified to the operating company, and the operating company presents the pending information to the development / maintenance company to take countermeasures against the abnormality. A maintenance method for a plant, which is characterized by responding to that effect from a company that performs. 5. The plant maintenance method according to claim 4, wherein the maintenance management device charges at least the use of the operating company.