WO2020070929A1 - Plant apparatus information management system - Google Patents

Abstract

Provided is a plant apparatus information management system which manages apparatus information of a plurality of plants by BOM, and manages, by WBS, information relating to operations performed for the plants. A maintenance code corresponding only to a device code in a lowermost layer, which is absolutely necessary to be input for all the plants, out of layers of the BOM and an operation code on a layer directly associated with apparatus information in a lowermost layer out of layers of the WBS is generated. A character string of related information corresponding to the apparatus information and the operation information is analyzed, and a group code corresponding to a specific character string is generated. A task application which performs a process relating to a plant management operation extracts the apparatus information and the operation information of the plurality of plants corresponding to the same maintenance code or group code and displays the information.

Description

Plant equipment information management system

The present invention relates to a plant equipment information management system.
Priority is claimed on Japanese Patent Application No. 2018-188498 filed on October 3, 2018, the contents of which are incorporated herein by reference.

In a plant such as a refuse incinerator, there is a lot of information on equipment, devices, and parts constituting the plant (hereinafter, referred to as “device information”), and information on work necessary for operating or maintaining the plant ( Hereinafter, there will be many “work information”. In order to manage these device information and work information, management methods such as BOM (Bill Of Materials) and WBS (Work Breakdown Structure) are used. BOM is list information obtained by subdividing device information into a hierarchical structure, and WBS is list information obtained by subdividing work information into a hierarchical structure. As described above, the BOM and the WBS appear to be separate items of list information that are not related to each other. However, in the case of operating a plant, for example, the device information of a certain layer of the BOM is compared with the device information of a certain layer of the WBS. By linking certain work information, plant management can be performed. For example, in Patent Document 1, device information managed by the BOM and work information managed by the WBS are linked, and information necessary for plant operation (hereinafter, referred to as “plant information”, at least (Including work information) has been proposed.

JP 2012-128761 A

Generally, when a BOM or a WBS is electronically managed by a computer, a code (hereinafter, referred to as an “apparatus code”) corresponding to each of a plurality of layers of the BOM is set in device information corresponding to each of the plurality of layers. A code (hereinafter, referred to as “work code”) corresponding to each of the work information corresponding to each of the plurality of hierarchies is set. When a worker inputs device information or work information, a corresponding device code or work code is automatically set.
Note that, here, BOM levels 1, BOM levels 2, BOM levels 3, and the like are sequentially numbered from top to bottom on each layer of the BOM to indicate a specific layer (specific BOM level). Similarly, each layer of the WBS is sequentially numbered WBS level 1, WBS level 2, WBS level 3 and the like from top to bottom to indicate a specific layer (specific WBS level).
Then, similarly to the management device of Patent Literature 1, plant information can be managed using a search code set based on a plurality of BOM-level device codes and WBS-level work codes. By setting such a search code, desired plant information can be searched and extracted from the plant information of a plurality of plants and compared.

However, when uniformly managing plant information of a plurality of plants that differ geographically and functionally, the number of hierarchies of the BOM and WBS of a certain plant (hereinafter, referred to as “plant 1”) and the other plants (hereinafter, referred to as “plant 1”) In some cases, the number of layers of the BOM and the WBS of “plant 2” may be different. For example, the BOM of the plant 1 may have five layers, while the BOM of the plant 2 may have three layers. The same applies to the WBS level. In this case, in order to uniformly manage the plant information of all the plants and search / extract the desired plant information, conventionally, even if the hierarchy is unnecessary in a certain plant, the plant with the highest hierarchy is used. You need to enter plant information according to the number of hierarchies. For example, if the BOM layer having the largest number of BOMs in all the plants is the same five layers as the plant 1, the BOM of the plant 2 is three layers. Unless a code (for example, a code meaning “not applicable”) is not set, the plant information of the plant 1 and the plant 2 cannot be searched and extracted at the same time. Therefore, in order to set a useless device code corresponding to the two hierarchies, the operator has to input some information corresponding to the device code as plant information. That is, it is necessary to identify an unnecessary hierarchy in accordance with the plant having the highest hierarchy in the BOM and the WBS, and to set a device code or a work code corresponding to the device information or the work information of all the hierarchy including the unnecessary hierarchy. For this reason, there was an excessive information input in which some plant information had to be input to all of these hierarchies. For this reason, the input operation by the operator takes a long time, and the cost tends to be high. Therefore, even when there are a plurality of plants having different numbers of hierarchies of the BOM and the WBS, there has been a demand for the development of a management system capable of reducing the load of input by an operator and searching, extracting, and comparing desired plant information.

In addition, when the information is excessively input in this manner, there is a high risk that the operator may incorrectly input the device information and the operation information, and as a result, there is a high possibility that the search, extraction, and comparison of the plant information will be hindered. . For example, as described above, when a search code is set based on a plurality of device codes corresponding to a plurality of BOM levels and a plurality of operation codes corresponding to a plurality of WBS levels, device information of a certain BOM level or a certain WBS level If the operator inputs the work information in error, a search code different from the original search code is set, so that it is not possible to extract and compare all the desired plant information. Therefore, there has been a demand for the development of a management system that minimizes the possibility that the search, extraction, and comparison of plant information may be hindered by erroneous input by an operator.

In addition, as the operation of the plant continues, various related information such as work details, operation know-how, and communication items are recorded and accumulated in the management system. The management system has been required to have a function capable of searching, extracting, and comparing plant information having a record of similar related information.

The present invention provides a plant equipment information management system that can solve the above-mentioned problems.

The plant equipment information management system of the present invention manages equipment information of a plurality of plants by a BOM, sets device codes respectively corresponding to the equipment information input corresponding to a plurality of layers of the BOM, And a work code corresponding to each of the work information input in correspondence with a plurality of layers of the WBS. The plant equipment information management system, wherein: Among the plurality of layers, the device code corresponding to the device information of the lowest layer in the layers in which the device information is always input in all of the plurality of plants, and among the plurality of layers of the WBS, Maintenance corresponding only to the work code corresponding to the work information in the WBS layer directly linked to the device information in the lowest layer A maintenance code generation unit that generates a maintenance code, a business application that executes processing related to the management work of the plant using the maintenance code, the device information and the work information corresponding to the maintenance code, and the device information. And a related information analyzing unit for analyzing a character string of related information corresponding to the work information; and a group code generating unit for generating a group code corresponding to a specific character string among the character strings, The application extracts and displays the device information and the work information of the plurality of plants corresponding to the same maintenance code or the same group code.

According to this configuration, the maintenance code for extracting the plant information includes the device code corresponding to the device information at the lowest layer in the BOM hierarchy in which the device information is always input in all of the plurality of plants. Since it is generated corresponding to only two work codes corresponding to the work information of the WBS layer directly linked to the device information, it is possible to avoid the situation of excessive information input as described in the above problem. For example, when the BOM of a certain plant has five layers and the BOM of another plant has three layers, the maintenance code is the WBS level directly linked to the device code corresponding to the device information of BOM level 3 and the device information. Is generated in correspondence with only the work code corresponding to the work information (for example, work information of the WBS level 1), the worker in the other plant does not have to use the equipment for the five layers but the equipment for the three layers. All you have to do is enter the information.

In addition, when the operator inputs device information and operation information, sufficient attention should be paid only to the input to the BOM level of the lowest layer necessary for generating the maintenance code and one WBS level directly linked to the BOM level. Even if there is an error in input of information for another BOM level or WBS level, desired plant information can be extracted. Although the extracted plant information includes some erroneous information, most of the extracted plant information is correct plant information. Therefore, the worker efficiently performs the plant management work using the business application. be able to.
In other words, when there are a plurality of plants, the load of the plant information input by the operator can be reduced, and even if there is an erroneous input of the plant information, the plant equipment information that can search, extract, and compare the desired plant information with high accuracy A management system can be provided.

In addition, since a group code can be generated in association with a specific character string included in related information corresponding to device information and work information, plant information in which a specific character string common as related information is recorded can be searched.・ Can be extracted and compared.

In the plant equipment information management system of the present invention, after the business application displays the equipment information and the work information of the plurality of plants corresponding to the same maintenance code, the group code generation unit displays the group code. The group code may be generated based on the specific character string included in the device information and the related information corresponding to the work information.

With this configuration, it is possible to generate a group code based on a specific character string included in the related information while referring to related information of a plurality of plant information linked by the same maintenance code. As a result, a plurality of plant information items linked by the same maintenance code can be further divided into groups, and search, extraction, and comparison can be performed on the group.

In the plant equipment information management system of the present invention, the analysis may be a text mining analysis.

According to this configuration, for a plurality of plant information input to the management system, the number of appearances and relevance of words and phrases included in the related information of the plant information can be automatically analyzed and displayed. . As a result, it is possible to easily select a “specific character string” used for grouping the plant information to which the same maintenance code is assigned.

The plant equipment information management system of the present invention further includes a database that stores the maintenance code, the group code, the equipment information and the work information corresponding to the maintenance code, and wherein the database is a first database. And a second database, wherein the business application executes a process related to the first work to obtain first work information, and a second business process that performs a process related to a second work different from the first work. A second business application that obtains work information, the first business application stores the first work information in the first database in addition to the device information and the work information, and the second business application , The maintenance code stored in the first database, The group code, the device information, the work information, and the first work information are copied to the second database to execute a process related to the second work, and the second work information is associated with the maintenance code and the It may be configured to be stored in two databases.

According to this configuration, the first business application and the second business application each have separate databases (first database and second database), and the second business application stores the contents of the first database in the second database. To perform the second operation. Therefore, for example, even when a maintenance work such as a periodic inspection is performed on the first database, the processing of the second business application can be executed using the second database, thereby improving the convenience of the plant equipment information management system. be able to.

According to the plant equipment information management system described above, when a plurality of plants are managed, the load of input of plant information by an operator is reduced, and desired plant information is searched, extracted, and compared with high accuracy. Can be. Further, it is possible to search, extract, and compare plant information including a specific character string in the related information by using the related information accumulated with the operation of the plant.

It is a block diagram of a plant equipment information management system which is an embodiment concerning the present invention. FIG. 2 is a diagram illustrating a business process of the plant equipment information management system in FIG. 1. FIG. 4 is a diagram illustrating a method for generating a maintenance code according to the present invention. 2 is a list showing device information, work information, and related information used by each processing unit of the business application unit 12 shown in FIG. 1. It is the 1st figure which is a display example of the plant information etc. of a comparison object in the present invention. It is a 2nd figure which shows the example of a display of plant information etc. of a comparison object in the present invention. It is the 3rd figure which shows the example of indication of the plant information and the like of the comparison object in this invention. FIG. 14 is a fourth diagram illustrating a display example of plant information and the like to be compared in the present invention. It is a figure showing the example of a display of the analysis result of related information in the present invention. It is a figure showing an example of a group code in the present invention.

<Embodiment>
Hereinafter, a plant equipment information management system according to an embodiment of the present invention will be described with reference to FIGS.
FIG. 1 is a block diagram of a plant equipment information management system according to an embodiment of the present invention.
The plant equipment information management system 10 (hereinafter, referred to as “management system 10”) is used for plant information such as refuse incinerators (equipment information, work information, or other information related thereto (hereinafter, “related information”)). Is a system that manages electronically. The management system 10 is configured by one or more personal computers (referred to as personal computers or PCs (personal computers)) and computers such as server devices. The management system 10 manages device information of a plurality of plants to be managed by a BOM, and manages work information by a WBS. Further, the management system 10 manages the BOM and the WBS in association with each other. Further, the management system 10 uniformly manages plant information of a plurality of plants that are geographically and functionally different. Therefore, the number of layers of BOM and WBS of one plant may be different from the number of layers of BOM and WBS of another plant.
In the present embodiment, as an example, among all the plants handled, the BOM hierarchy is the largest in a plant in which device information exists up to BOM level 5 (BOM Lv.5), and the WBS hierarchy is The management system 10 will be described assuming that the largest is a plant having work information up to WBS level 3 (WBS Lv.3). It is for this reason that BOM is described up to BOM level 5 and WBS is described up to WBS level 3 in the list of FIG. 4 described later.

The management system 10 includes an input / output unit 11, a business application unit 12, and a storage unit 13.
The input / output unit 11 includes at least a keyboard for inputting plant information by a worker and a monitor for outputting and displaying plant information. The input / output unit 11 may be integrated with the monitor by a touch panel. The input / output unit 11 may include a printer that outputs and prints plant information.

As described later, plant operation management begins with customer equipment ledger creation processing for initial registration of plant information, process schedule creation processing for inspection and maintenance work planning, and actual maintenance work. It is performed in accordance with a series of business processes (see FIG. 2) such as a construction report creation process to be input. Therefore, the business application unit 12 includes a plurality of processing units for performing processing according to the process. Specifically, the business application unit 12 includes, as processing units, a maintenance code generation unit 120, a group code generation unit 12A, a customer equipment ledger creation unit 121, a process table creation unit 122, and an estimate creation unit 123. , A construction specification creator 124, a construction report creator 125, a construction daily report creator 126, a maintenance history creator 127, a maintenance plan creator 128, and a related information analyzer 129. Details of the processing of each of these processing units will be described again after the description of the storage unit 13.
The maintenance code COM (COM is an abbreviation of Code Of Maintenance) generated by the maintenance code generation unit 120 and the group code PARE generated by the group code generation unit 12A are one type of search code, and are important for the present invention. It is one of the components. As described later, the group code PARE is associated with a part of the plant information among a plurality of plant information associated with a specific maintenance code COM. Therefore, by appropriately using one or both of these two codes, when a plurality of plants are managed, the load of input of plant information by an operator can be reduced, and desired plant information can be searched with high accuracy. Can be extracted and compared.
The group code was named "PARE" for the following reason. First, “PARE” has the meaning of “removing extra parts” in English, and removes unnecessary information as a kind of search code and extracts only necessary information, so that a management system 10 that compares a plurality of plant information. In the above, the inventor considered that the name was appropriate. Further, the group code PARE has a high correlation with the maintenance code COM, and when "COM" and "PARE" are combined, it becomes "COMPARE" (meaning "comparison" in English), and a management system for comparing a plurality of plant information. This is because, in 10, the inventor considered that the name is still appropriate.

The storage unit 13 stores the plant information processed by the business application unit 12. The storage unit 13 stores the plant information processed by the customer equipment ledger creation unit 121 and the maintenance code COM generated by the maintenance code generation unit 120. The customer BOM / WBSDB 131 stores the processing information. The construction schedule DB 132 in which the plant information stored and stored is stored, the estimation DB 133 in which the plant information processed by the estimation creating unit 123 is stored and stored, and the plant information processed by the construction specification creating unit 124 is stored and stored. The stored order cost DB 134, the equipment inspection / measurement record DB 135 in which the plant information processed in the construction report creation unit 125 is stored and saved, and the plant information processed in the construction daily report creation unit 126 are stored and saved. And the plant information processed by the maintenance history creation unit 127 are stored and stored. The thing history DB137, plant information that has been processed in the maintenance planning unit 128 is provided with a future work plan DB138 to be stored and saved. That is, among the respective processing units of the business application unit 12, DBs respectively corresponding to the respective processing units 120 to 128 except the group code generation unit 12A and the related information analysis unit 129 are provided.
"DB" means a database. These DBs 131 to 138 may be separate storage devices, or may be different storage areas in one storage device. The DBs 131 to 138 may be geographically and spatially separated from each other as long as they are connected to the business application unit 12 and the input / output unit 11 via the Internet or the like by wire or wirelessly.

Now, the processing of each processing unit of the business application unit 12 will be described in detail with reference to FIGS. 1, 2, 3, 4, 9, and 10. FIG. FIG. 2 is a diagram showing a business process of the plant equipment information management system of FIG. FIG. 3 is a diagram illustrating a method for generating the maintenance code COM.
FIG. 4 is a table showing device information and work information used in each processing unit for each corresponding BOM level or WBS level. FIG. 4 also shows related information that is input or used in each processing unit. In FIG. 4, an item with “-” is an item that is not used in the corresponding processing unit. Therefore, the item and an input column for inputting the item are displayed on the monitor of the input / output unit 11. Not done. However, if plant information is input in the upstream business process in the DB provided individually corresponding to each processing unit, the plant information of the item with “-” is also stored in the DB. Since the information is stored, if the operator desires to display the item, the item can be displayed by appropriately selecting the item.
FIG. 9 is a diagram illustrating a display example of the analysis result of the related information. FIG. 10 is a diagram illustrating an example of the group code PARE.
It should be noted that the group code generation unit 12A and the related information analysis unit 129 are used to generate the group code PARE in the other processes S12 to S18 except for the customer device ledger creation process S11 among the processes described below. Processes used by the schedule creation unit 122, the estimation creation unit 123, the construction specification creation unit 124, the construction report creation unit 125, the construction daily report creation unit 126, the maintenance history creation unit 127, or the maintenance plan creation unit 128 as appropriate. Department.

(Create customer ledger)
First, the customer equipment ledger creation unit 121 displays a “customer equipment ledger screen” on the monitor of the input / output unit 11. The customer equipment ledger creation unit 121 executes a customer equipment ledger creation process S11 for a new plant in which the plant information is not stored and stored in the storage unit 13. On the “customer device ledger screen”, input fields for a plurality of items to be input in the customer device ledger creation process S11 are displayed.
Specifically, as shown in FIG. 4, customer information such as customer equipment name (BOM level 1), customer equipment name or equipment specification (BOM level 2), equipment specification classification, customer equipment detail name, equipment information Detailed specification or series (BOM level 3), customer equipment part name or partial specification (BOM level 4), customer equipment part name or part specification (BOM level 5), and work attribute or customer as work information The customer device ledger creation unit 121 displays an input field for inputting an execution item name (WBS level 1) and a customer work detail name (WBS level 2) on the monitor of the input / output unit 11. The operator makes appropriate entries in these input fields using the keyboard of the input / output unit 11, and electronically creates a ledger (master data) of plant information of the new plant. In the ledger, as described later, the maintenance code COM, the device information of the BOM, the work information of the WBS, and the related information are linked to each other.

Here, the “customer device ledger screen” corresponds to device information of BOM level 1 to BOM level 5 and work information of WBS levels 1 and 2 as items to be input in the creation process S11 of customer device ledger. Although an input field is displayed, the equipment information is always input from BOM level 1 to BOM level 3 in all the plants handled, and the work information is always input in WBS level 1 from all the plants handled. The explanation is advanced as it is. That is, among all the plants handled, there may be a plant that does not need to input BOM level 4 and BOM level 5 device information and a plant that does not need to input WBS level 2 work information.
Then, the customer equipment ledger creating unit 121 stores and saves the plant information input by the operator on the “customer equipment ledger screen” in the customer BOM / WBSDB 131.

The “sequence” (BOM level 3) is information for distinguishing a plurality of devices and devices of the same type when these devices and devices are arranged. In the case of a furnace, it is also referred to as “reactor” information, and the corresponding device code is also referred to as a “reactor code”. For example, when a plurality of refuse incinerators are provided in one refuse incineration plant, different unit codes are set to distinguish each refuse incinerator.

(Maintenance code COM generation processing)
The maintenance code generation unit 120 is configured to correspond to a specific combination of the device code and the work code corresponding to the device information and the work information input on the “customer device ledger screen”, and to perform the maintenance code COM, which is a type of the search code. Generate Specifically, among the plurality of layers of the BOM, the device code corresponding to the device information of the lowest layer among the layers in which the device information is always input in all of the plurality of plants (in the present embodiment, the BOM level 3 A device code corresponding to the device information) and a work code corresponding to the work information of the WBS layer directly linked to the device information of the lowest layer among the plurality of layers of the WBS (in this embodiment, WBS level 1 The maintenance code generation unit 120 generates the maintenance code COM only in correspondence with the operation code corresponding to the operation information of (1).
Then, the generated maintenance code COM is displayed on the “customer equipment ledger screen” on the monitor, and the customer equipment ledger creation unit 121 is linked to the plant information input on the “customer equipment ledger screen”. Then, it is stored and stored in the customer BOM / WBSDB 131. The details are described below.

FIG. 3 is a simplified diagram for explaining a method of generating the maintenance code COM. FIG. 3A shows an example of the device information of each layer of the BOM having the plant name “plant α”.
For example, the plant α is composed of “Equipment 1” and “Equipment 2” which are BOM level 1 equipment information. The equipment 1 is associated with “equipment A” and “equipment B”, which are the equipment information of the BOM level 2. The equipment 2 is linked to “equipment C” which is the BOM level 2 equipment information.
The device A is linked to “device details 1” and “device details 2”, which are device information of BOM level 3. The device B is linked to “device details 3”, which is device information of BOM level 3. The device C is linked to “device details 4” which is device information of BOM level 3.
The device detail 1 is linked to “part 1” which is BOM level 4 device information, and the portion 1 is linked to “part 1” which is BOM level 5 device information.
It should be noted that there is no BOM level 4 or device information deeper than that at the BOM level associated with the device details 2, 3, and 4.
Here, the device information of the BOM levels 1 to 3 is information that is always input in any plant managed by the management system 10. The device information of the BOM levels 4 and 5 is information for which the necessity of input depends on the type of the device information input to the BOM levels 1 and 3 and the characteristics of the plant. Note that the BOM hierarchies for which input by the operator is indispensable are BOM levels 1 to 3 here, but this is merely an example, and the number of hierarchies for which input is required is set as appropriate according to the specifications of the management system 10. May do it. For example, two hierarchies of BOM levels 1 and 2 may be set as hierarchies that require input. Further, the BOM may have a hierarchy deeper than the BOM level 5 (for example, the BOM level 6, the BOM level 7,...).

FIG. 3B shows an example of the work information of each layer of the WBS of the plant α. "Work 1" which is work information of WBS level 1 is linked to "work details A" and "work details B" which are work information of WBS level 2 respectively. "Work 2" which is work information of WBS level 1 is linked to "work details C" which is work information of WBS level 2. The work detail A is linked to “work detail 1” which is work information of WBS level 3. There is no work information of the WBS level 3 or a hierarchy deeper than that associated with the work details B and the work details C.
Here, the work information of the WBS level 1 is information that is always input in any plant managed by the management system 10. The work information of the WBS levels 2 and 3 is information for which the necessity of the input depends on the type of the work information input to the WBS level 1 and the characteristics of the plant. The level of the WBS for which the input by the operator is indispensable is WBS level 1 here, but this is merely an example, and the number of the levels for which the input is required is appropriately set according to the specification of the management system 10. Good. For example, two hierarchies of WBS levels 1 and 2 may be set as hierarchies that require input. Further, the WBS may have a hierarchy deeper than the WBS level 3 (for example, WBS level 4, WBS level 5, ..., etc.).

The BOM and the WBS of the plant α shown in FIGS. 3A and 3B are linked to each other as shown in FIG. 3C. That is, among the BOM hierarchies (BOM levels 1 to 3 in this example) that must be input in all the plants managed by the management system 10, the input is similarly required in the device information of the BOM level 3 which is the lowest layer. Of WBSs (in this example, WBS level 1), work information of WBS1, which is a hierarchy directly linked to BOM level 3 device information, is linked. In FIG. 3C, “work 1”, which is work information of the WBS1, is linked to “device details 1” that is device information of the BOM level 3.
In the WBS hierarchy, the work information of the hierarchy that is “directly linked” to the BOM level 3 device information is the work information that can be performed on the BOM level 3 device information that is the lowest layer. It means the work information of the uppermost layer among a plurality of WBS layers. Therefore, when a plurality of pieces of work information of the WBS level 1 do not exist for a plurality of pieces of device information of the BOM 3 level and there is only one piece of work information, the WBS level 1 does not become the above-mentioned “directly linked” hierarchy. . For example, in FIG. 3B, when the work information of the WBS level 1 is only “work 1” and “work 2” does not exist, the work information is directly linked to the BOM level 3 device information in the WBS hierarchy. The tier can be WBS level 2 instead of WBS level 1.

Next, as shown in FIG. 3C, the BOM and WBS in FIGS. 3A and 3B relate to the plant information of the plant name “plant α”. Linked to BOM and WBS.
Further, as shown in FIG. 3C, the maintenance code COM corresponding to only “device details 1” that is the device information of the plant α and “work 1” that is the work information of the plant α is generated by the maintenance code generation unit. 120 and are similarly linked. The maintenance code COM is, for example, the device code automatically set by the business application unit 12 in response to the input of “apparatus details 1” by the operator is “123XA”. When the work code automatically set by the business application unit 12 in response to the input by the worker is “089X”, “123XA089X” is generated in correspondence with only these two codes. You.

In addition, the case where the device code is “123XA” and the operation code is “089X” has been described as an example, but the number of digits of these codes is not limited to this, and may be set to be more or less depending on specifications or the like. sell. Further, the maintenance code generation unit 120 may generate the maintenance code COM by using the automatically generated device code and the operation code as they are, or may store a two-input one-output conversion table or conversion in the storage unit 13. A maintenance table may be separately provided, and the maintenance code generation unit 120 may generate the maintenance code COM using the table. For example, when the device code is “123XA” and the operation code is “089X”, the maintenance code generation unit 120 may arrange the devices as they are and generate a maintenance code COM such as “123XA089X” or “089X123XA”. Alternatively, the maintenance codes COM may be generated in a mixed manner such as “102839XXA” (alternately arranged). In addition, the maintenance code generation unit 120 inputs the device code “123XA” and the work code “089X” to the conversion table, and outputs a code (a value completely unrelated to the device code or the work code) output from the conversion table. Or the number of digits, the only code corresponding to these two codes) may be the maintenance code COM.

(Process creation of process chart)
Returning to the description of FIG. First, the process table creation unit 122 copies the maintenance code COM stored and stored in the customer BOM / WBSDB 131 by the customer device ledger creation unit 121 and all the plant information associated therewith into the construction schedule DB 132. Then, the process schedule creation unit 122 displays a “process schedule creation screen” on the monitor of the input / output unit 11 and executes the process creation process S12 using the construction schedule DB 132. On the “process chart creation screen”, input fields for a plurality of items input in the process chart creation process S12 are displayed. Specifically, as shown in FIG. 4, the customer information includes customer equipment name (BOM level 1), equipment specification classification, customer equipment detail name, equipment detail specification, or series (BOM level 3), and Work attribute or customer execution item name (WBS level 1) as work information, customer work detailed name (WBS level 2), planned process or planned man-hour (WBS level 3), and related information such as shutdown schedule or The process chart creating unit 122 displays an input field for inputting an inspection schedule or the like on the monitor of the input / output unit 11. In the related information input field, a description or a comment can be input in text. For example, it is possible to input various kinds of information such as detailed contents regarding scheduled shutdown and inspection, and information to contact customers.
Therefore, the related information may include know-how based on the experience of the worker, the model number of the specific product, and secret information on the work.
At this time, in the construction schedule DB 132, the maintenance code COM and the plant information stored and stored in the customer BOM / WBSDB 131 are copied. Therefore, in the case of the process list creation process S12, regarding the items that need to be input and the plant information or the like that has already been copied, the process list creation unit 122 uses these items when displaying the input column. Information and the like are also displayed. In the example of FIG. 4, the plant information and the like that need to be input by the customer equipment ledger creation unit 121 and the process table creation unit 122 are the same at the BOM level 1, the BOM level 3, the WBS level 1, and the WBS level 2. is there. Therefore, it is not necessary for the operator to input these plant information again on the “process chart creation screen”. However, the operator can correct these information in the input fields of the “process chart creation screen”.
Therefore, in the process S12, the operator needs to newly input at most two items of the planned process or the planned man-hour (WBS level 3) and the related information. The time and labor for input work can be reduced.

In addition, when the process chart creation process S12 is performed for a specific plant, the process chart creation unit 122 searches for plant information of a plurality of plants associated with the same maintenance code COM that is used for creating the process chart. It can be extracted and displayed on the monitor of the input / output unit 11 in a format that can be compared with other plants. Therefore, when the worker executes the creation process S12, the work can be performed efficiently while comparing with other plants, so that the time and labor of the input work of the worker can be reduced.
By the way, according to the present invention, as described above, when displaying plant information and the like of a plurality of plants associated with the same maintenance code COM on a monitor, if a large number of the plurality of plant information and the like are displayed, the operation The user can further narrow down and display the displayed plant information with the group code PARE. The method of generating the group code PARE and linking it to the plant information is as follows.
First, the operator instructs the process chart creating unit 122 via the “process chart creating screen”, so that the process chart creating unit 122 activates the related information analysis unit 129. The related information analysis unit 129 analyzes a character string such as a specific word or number from a huge text stored and stored in the construction schedule DB 132 as related information of the plurality of displayed plant information (for example, text mining analysis). Then, as shown in the upper diagram of FIG. 9, a predetermined number of specific character strings are displayed on the monitor in descending order of the number.
Although details will be described later, when the operator selects a specific character string displayed on the monitor, only a character string highly relevant to the selected specific character string is displayed as shown in the lower diagram of FIG. . Here, when the operator desires the above-described narrowing down by the selected specific character string, the operator instructs the process chart creating unit 122 via the monitor, and the process chart creating unit 122 creates the group code. Activate the unit 12A. The group code creating unit 12A creates a specific group code PARE corresponding to the selected specific character string on a one-to-one basis, and displays the “group of multiple plants linked to the same maintenance code COM” already displayed on the monitor. In the “information”, the selected specific character string is linked to the plant information included in the related information. For example, when the group code PARE is generated as “X425A00A1”, FIG. 10 shows a state where the group code PARE is linked to the plant information in FIG. 3C.
Note that the group code PARE has been described as “X425A00A1” as an example, but the number of digits of the code is not limited to this, and may be set to be more or less depending on specifications and the like.

When the group code PARE is generated by the group code generation unit 12A, the group code PARE is displayed on the “process chart creation screen”. Further, the process chart creating unit 122 stores and saves the group code PARE in the construction schedule DB 132 in association with the corresponding plant information.
Accordingly, the operator can execute the narrowing down by using the group code PARE, reduce the number of the plurality of plant information displayed on the monitor, and display only the information highly relevant to the work. The work can be performed more efficiently while comparing with other plants. Therefore, it is possible to reduce the time and labor of the input operation of the worker.
In each of the following processes S13 to S18 of the business process, each of the processing units 123 to 129 can generate a group code PARE and link it to the corresponding plant information, similarly to the process table creation unit 122.

As described above, when the process chart creation process S12 is performed for a specific plant, the plant information of a plurality of plants associated with the same maintenance code COM and the same group code PARE is searched and extracted, and other plants are searched. It can be displayed on the monitor of the input / output unit 11 in a format that can be compared with. This allows the worker to perform input with respect to a specific plant with reference to other plant information, so that the input operation becomes efficient (time reduction, labor reduction), and the plant information based on the actual results is saved. Since the result is a comparison, a highly reliable process chart can be created.

(Estimate creation process)
First, the estimate creation unit 123 copies all of the maintenance code COM, the group code PARE, and the plant information associated therewith, which are stored and saved in the construction schedule DB 132 by the process chart creation unit 122, to the estimate DB 133. Since all the plant information and the like stored and stored in the construction schedule DB 132 are copied, the BOM level 2 and the BOM level 4, which are not used in the process table creation process S12 in the process table creation unit 122 and are not displayed on the monitor, are used. And the plant information of the BOM level 5 are also copied to the estimation DB 133. The BOM level 2, BOM level 4, and BOM level 5 plant information is the same as the plant information stored and stored in the customer BOM / WBSDB 131.

Then, the estimate creating unit 123 displays an “estimate creation screen” on the monitor of the input / output unit 11, and executes the estimate creation process S13 using the estimate DB 133. In the “estimation creation screen”, input fields for a plurality of items to be entered in the estimate creation processing S13 are displayed. Specifically, as shown in FIG. 4, the customer information includes customer equipment name (BOM level 1), customer equipment name (BOM level 2), equipment specification classification, customer equipment detail name, or series (BOM). Level 3), customer equipment part name, part specification, quantity, or estimated unit price (BOM level 5), and work attribute or customer execution item name (WBS level 1) as work information, customer work detail name, The estimate creation unit 123 displays on the monitor of the input / output unit 11 an input field for inputting the estimated man-hour or the estimated unit price (WBS level 2), and furthermore, the expenses as the related information.
At this time, the maintenance code COM, the group code PARE, and the plant information stored and stored in the construction schedule DB 132 are copied to the estimate DB 133. Therefore, in the case of the estimate creation processing S13, regarding the items that need to be input and the already copied plant information, etc., the estimate creation unit 123 displays these information and the like when displaying the input column. Is also displayed.

Here, in FIG. 4, the BOM level 2 information that needs to be input in the customer device ledger creation unit 121 is the customer device name or the device specification, whereas the BOM level that the estimate creation unit 123 needs to input is The information of No. 2 is a customer device name, and it is not necessary to input device specifications. In this case, the quotation creating unit 123 displays the customer device name copied from the construction schedule DB 132 to the quotation DB 133 in the input field of the “quotation creation screen”, and allows the operator to make corrections as necessary. Similarly, there is no need to display the copied device specifications. In FIG. 4, the BOM level 5 information that needs to be input by the customer equipment ledger creation unit 121 is the customer equipment part name or the component specification, whereas the BOM level that the estimate creation unit 123 needs to input is The information No. 5 is a customer equipment part name, a part specification, a quantity, or an estimated unit price, and the information amount is increasing. In this case, the estimate creation unit 123 displays the customer equipment part name or the part specification copied from the construction schedule DB 132 to the estimate DB 133 in the input field of the “estimate creation screen”, and corrects it by the operator as necessary. Although possible, an input field corresponding to information (here, quantity or estimated unit price) increased within the same BOM level is newly displayed on the “estimation creation screen” to prompt the operator to input.

Note that, similar to the process table creation unit 122, when the estimation creation process S13 is performed for a specific plant, a group code PARE can be generated and linked to the plant information. Then, the quotation creating unit 123 can search and extract plant information of a plurality of plants associated with the same maintenance code COM and plant information of a plurality of plants associated with the same group code PARE, and can compare with other plants. It can be displayed on the monitor of the input / output unit 11 in a format. This allows the worker to perform input with respect to a specific plant with reference to other plant information, so that the input operation becomes efficient (time reduction, labor reduction), and the plant information based on the actual results is saved. Since the result is a comparison, a highly reliable estimate can be created. In particular, by displaying plant information of plants that are closely related to the same group code, work efficiency can be further improved, and a highly accurate estimate can be created.

The other processing units, that is, the construction specification creation unit 124 to the maintenance plan creation unit 128 perform the same operations as the process chart creation unit 122 or the estimate creation unit 123, and thus will be briefly described below. These processing units search and extract plant information of a plurality of plants associated with the same maintenance code COM and the same group code PARE, and monitor the input / output unit 11 in a format that can be compared with other plants. Can be displayed. In addition, each of these processing units can analyze the related information using the related information analysis unit 129, and can cause the group code generation unit 12A to generate a group code based on a specific character string selected from the analysis result.

(Creation of construction specifications)
First, the construction specification creator 124 copies the maintenance code COM, the group code PARE, and the plant information associated therewith, all stored and stored in the quotation DB 133 by the quotation creator 122, to the order cost DB 134. Then, the “construction specification document creation screen” is displayed on the monitor of the input / output unit 11, and the construction specification document creation process S14 is executed using the order cost DB 134.

(Construction report creation processing)
First, the construction report creation unit 125 copies the maintenance code COM, the group code PARE, and the plant information associated therewith, all stored and stored in the order cost DB 134 by the construction specification creation unit 124, into the equipment inspection / measurement record DB 135. I do. Then, the “construction report creation screen” is displayed on the monitor of the input / output unit 11, and the construction report creation process S15 is executed using the equipment inspection / measurement record DB 135.

(Create daily work report)
First, the construction daily report creation unit 126 copies the maintenance code COM, the group code PARE, and the plant information associated therewith, all of which are stored and stored in the device inspection / measurement record DB 135 by the construction report creation unit 125, to the construction result DB 136. . Then, the “construction daily report creation screen” is displayed on the monitor of the input / output unit 11, and the construction daily report creation processing S16 is executed using the construction result DB 136.

(Process of creating maintenance history)
First, the maintenance history creation unit 127 copies the maintenance code COM, the group code PARE, and the plant information associated therewith, all stored and stored in the construction result DB 136 by the construction daily report creation unit 126, to the construction history DB 137. Then, a "maintenance history screen" is displayed on the monitor of the input / output unit 11, and the maintenance history creation process S17 is executed using the construction history DB 137.

(Maintenance plan creation processing)
First, the maintenance plan creation unit 128 copies the maintenance code COM, the group code PARE, and the plant information associated therewith, all of which are stored and stored in the construction history DB 137 by the maintenance history creation unit 127, into the future construction plan DB 138. Then, a "maintenance plan creation screen" is displayed on the monitor of the input / output unit 11, and the maintenance plan creation process S18 is executed using the future construction plan DB 138.

Then, after the maintenance plan creation process S18, the business process in the management system 10 returns to the process chart creation process S12, and continues the business process sequentially. When the business process returns to the process chart creation process S12, the process chart creating unit 122 firstly executes the maintenance code COM, the group code PARE, and the maintenance code COM stored and saved in the future construction plan DB 138 by the maintenance plan creating unit 128. All the plant information associated with them is copied to the construction schedule DB 132, and the maintenance code COM newly stored and stored in the customer BOM / WBSDB 131 by the customer equipment ledger creation unit 121 and all the plant information associated therewith are constructed. Copy it to the schedule DB 132.
As described above, in the management system 10, the processing units 120 to 128 of the business application unit 12 are provided with the DBs respectively corresponding to the processing units. Therefore, when a maintenance work such as a periodic check is performed on the DB corresponding to the immediately preceding business process, the processing unit corresponding to the business process to be executed at the present time uses the DB individually corresponding to itself. It can execute its own processing. Therefore, the convenience of the management system 10 can be improved.

(Display example)
Next, a display example on a monitor when a plurality of pieces of plant information are searched and extracted with the same maintenance code COM will be described with reference to FIGS. 5 to 8. A display example on the monitor when a plurality of plant information items are searched and extracted with the same group code PARE is the same as that in the case of COM, and thus will not be described.
When the construction daily report creation unit 126 executes the construction daily report creation processing S16, the actual man-hours (work information of the WBS level 2) is input on the “construction daily report creation screen”. These display examples are as follows. This is an example in which other reference plant information is searched and extracted with the same maintenance code COM and displayed on a monitor. Even if the plant information is the same, the management system 10 indicates that the operator can select any one of the display formats shown in FIGS. 5 to 8.
Here, among the plurality of layers of the BOM, “No. 1 boiler tube” is input as the BOM level 3 device information which is the lowest layer among the layers in which the device information is always input in all of the plurality of plants. An example in which “boiler tube cleaning” is input as work information of WBS level 1 which is the WBS layer directly linked to the device information of the lowest layer among a plurality of layers of WBS. The product code corresponding to “No. 1 boiler tube” is “103AA01”, the work code corresponding to “Boiler tube cleaning” is “0201”, and the maintenance code COM is “103AA010201” using these as they are. This is an example.
As described above, the number of digits of the product code and the like can be appropriately set according to the specifications and the like. Here, the number of digits is larger than the number of digits of the product code described with reference to FIG. Although the product code is “103AA01”, this is an example in which the reactor code “01” (meaning Unit 1) is particularly included in the product code.
In addition, in FIGS. 5 to 7, the presence / absence of the result is also displayed as the related information as “レ” when there is a result, and as “−” when there is no result.
Here, an example is shown in which the construction daily report creation unit 126 executes the construction daily report creation processing S16, but the operator can similarly select a display format in other processing units of the business application unit 12. .

FIG. 5 shows, from all the plant information stored and maintained in the storage unit 13, the plant information on which the “boiler tube cleaning” of the “No. 1 boiler tube” has been performed or is to be performed, with the maintenance code COM “103AA010201”. This is an example of searching, extracting, and displaying on a monitor for comparison.
It can be seen that BOM level 3 of the listed plant information is all “No. 1 boiler tube”, and WBS level 1 is all “Boiler tube cleaning”. In addition, BOM level 4 has two different pieces of equipment information, “No. 1 boiler tube furnace left side wall pipe” and “No. 1 boiler tube furnace right side wall pipe”, and WBS level 2 has “cleaning” and “meat”. It can be seen that there are three different pieces of work information of "polishing thickness measurement location" and "thickness measurement". Further, WBS level 3 includes “1 pass cleaning”, “2 pass cleaning”, “cleaning ash removal”, “measurement location marking”, “measurement location polishing”, “thickness measurement A”, and “thickness measurement B”. It is understood that there are seven different pieces of work information.

Also, looking at the columns of the actual man-hour and the actual (presence / absence), "No. 1 boiler tube furnace left side wall tube" has the actual work and the man-hour is also displayed. On the other hand, since “No. 1 boiler tube furnace right wall pipe” has no work record, it can be seen that the man-hour is not displayed.
The plant information displayed as shown in FIG. 5 is not easy to understand at a glance as to how many actual man-hours are obtained only by “cleaning” of WBS level 2. Therefore, in the display example of FIG. 6, the actual man-hours are added and displayed collectively in three different pieces of work information of “cleaning”, “polishing of a thickness measurement location”, and “thickness measurement” of WBS level 2. is there. It can be easily understood that the actual man-hour for "cleaning" is "4", the actual man-hour for "polishing thickness measurement location" is "4", and the actual man-hour for "thickness measurement" is "2". .
Further, when the user wants to know the total of the actual man-hours at the present time, it can be displayed as shown in FIG. Here, the proven results are “cleaning” of “No. 1 boiler tube furnace left side wall pipe” (actual man-hours: 4), “polishing of thickness measurement points” (actual man-hours: 4), and “thickness measurement” ( Since the actual man-hour is 2), these numbers are added, and the current total of the actual man-hours “10” is displayed.
7 can be further simplified, and the total “10” of the actual man-hours of “cleaning of the boiler tube” at the present time can be displayed as shown in FIG.

As described above, the product code and the specific WBS corresponding to the device information of the specific BOM level (the lowest layer among the multiple layers of the BOM, in which the device information is always input in all of the plurality of plants). The maintenance code COM corresponding to the work code corresponding to the work information of the level (the WBS layer which is directly linked to the device information of the lowest layer among the plurality of layers of the WBS) manages all the management codes managed by the management system 10. It is linked to the plant information. Therefore, if the operator searches the management system 10 using the maintenance code COM, it is possible to extract other plant information to be compared for reference at the time of input work. By appropriately selecting and comparing the display formats, it is possible to reduce the time and labor required for input work by the operator.

Since the maintenance code COM is a code corresponding to the plant information at both the specific BOM level and the specific WBS level, the maintenance code COM is searched using only the specific BOM level or the code corresponding to only the specific WBS level. The information to be extracted can be narrowed down remarkably as compared with the case where the information is extracted. Further, the specific BOM level is the lowest layer among the multiple layers of the BOM in which the device information is always input in all of the multiple plants, and the specific WBS level is the minimum of the multiple layers of the WBS. Of these, since it is the WBS layer directly linked to the equipment information of the lowest layer, even if an operator inputs plant information incorrectly to another layer, all other layers to be compared are to be compared. Plant information can be accurately searched and extracted with high accuracy.

As described in detail above, according to the management system 10 of the present embodiment, when a plurality of plants are to be managed, the load of input of plant information by an operator is reduced, and there is no erroneous input of plant information. However, desired plant information can be searched, extracted, and compared with high accuracy.

(Display example of analysis result of related information)
FIG. 9 is a diagram illustrating a display example of the analysis result of the related information by the related information analysis unit 129. In the upper diagram of FIG. 9, a display example of an analysis result in which the related information analysis unit 129 performs a text mining analysis on the related information linked to the same maintenance code COM stored in the DB 131 to 138 (for example, the construction result DB 136) It is. The example shown in the upper diagram of FIG. 9 is an analysis result of related information on boiler tube inspection and maintenance. The analysis result includes the number of appearances of each meaningful character string (specific character string such as a word, a number, a phrase, etc.) constituting the related information, and the relation between the character strings. Further, in the analysis result, for example, the number of appearances and correlation of character strings that can be classified into device information and work information are displayed on a monitor. Here, at first glance, the operator performs an operation of selecting “extubation” by paying attention to “extubation” which is a character string not related to “boiler tube inspection and maintenance”. Then, the display is switched to the display shown in the lower diagram of FIG. The lower part of FIG. 9 shows an analysis result obtained by performing the text mining analysis by the relevant information analyzer 129 on only the relevant information including “extub” among the relevant information targeted in the upper part of FIG. The lower part of FIG. 9 displays the number of appearances of each character string constituting a plurality of pieces of related information including “extubation” and the relevance between the character strings.
The worker refers to “the scaffold” having a frequency of 101 occurrences of “extubation” and 201 times of the “scaffold” having a correlation with “extubation”. Is important information. Based on this determination, if the operator wants to extract only the plant information including “extubation” in the related information and make the comparison possible, the operator generates the group code PARE based on “extraction” and returns to the corresponding plant information. Is performed to instruct each of the processing units 122 to 128 to link the data. Then, the group code generation unit 12A extracts only the plant information including the specific character string “extubation” from the plant information associated with the same maintenance code COM as the currently displayed plant information. The same group code PARE is assigned to the extracted plant information. FIG. 10 shows an example of the group code PARE.

Note that a plurality of group codes PARE can be linked to one plant information. For example, it is possible to generate a different group code PARE based on each of “extubation” and “scaffold” in the upper diagram of FIG. In this case, the plant information includes a group code PARE generated based on “extubation” (hereinafter, referred to as “PARE1”) and a group code PARE generated based on “scaffold” (hereinafter, “PARE2”). ) Can be generated. The plant information can be searched with any of the corresponding maintenance code COM, group code PARE1, and group code PARE2.
By the way, a predetermined capacity for storing a plurality of group codes PARE is prepared in advance in each DB of the storage unit 13. By associating the closely related plant information with the group code PARE, the worker can search and extract the plant information not only by the maintenance code COM but also by the group code PARE in each of the processes of S12 to S18 in FIG. , Makes comparisons possible.

A group consisting of a plurality of plant information items associated with one group code PARE (for example, “X425A00A1”) is associated with a maintenance code COM (for example, “123XA089X”) corresponding to the plant information item. A relationship included in a group including a plurality of plant information is established. Further, as described above, it is possible to generate a plurality of group codes PARE corresponding to one certain maintenance code COM. By generating a large number of group codes PARE with reference to the analysis result of the related information analysis unit 129 and performing a large number of groupings of the plant information, it is possible to increase the processing speed and processing accuracy in each of the processes S12 to S18.

As an example of a specific character string used for grouping, in addition to a character string having a large number of appearances, a number related to cost or actual man-hour can be used. The cost and the actual man-hour have a high degree of influence on the business, and a character string with a large number of appearances indicates that the degree of influence on the business and customer needs are high. By referring to the analysis result of the related information analysis unit 129 and grouping the plant information including a specific character string having a large influence on customer needs and business policies in the related information based on the experience of the worker, each processing unit More effective processing can be performed in steps 122 to 128.

関 連 In addition, related information includes many tacit knowledge (knowledge) of field workers. By performing text mining analysis and the like by the related information analysis unit 129, it is possible to visualize unknowable correlations and the like of character strings constituting related information, and to make use of the know-how of field workers. In addition, the number of occurrences of a specific character string can be automatically calculated for a large amount of text information. As a result, it is possible to grasp the importance, the degree of influence, and the like of the character strings that could not be recognized so far, and perform effective grouping.

In the above description, the related information analyzing unit 129 displays the analysis result of the related information. In addition, the related information analyzing unit 129 learns which character string is selected as the specific character string, and becomes a selection candidate. It may be configured to display character string candidates. For example, when a character string having a large number of appearances tends to be selected, the related information analysis unit 129 may highlight and display the top three character strings in descending order of the number of appearances. Displaying with emphasis means, for example, displaying with a larger font size, displaying in bold, displaying in red, or the like. Further, for example, when a character string (numerical value) indicating a cost or man-hour that has a correlation with a certain character string α is larger than a predetermined value, the related information analysis unit 129 emphasizes the character string α as a specific character string candidate. May be displayed.

Otherwise, it is possible to appropriately replace the components in the above-described embodiment with known components without departing from the spirit of the present invention. The technical scope of the present invention is not limited to the above embodiment, and various changes can be made without departing from the spirit of the present invention. For example, the related information analysis unit 129 may perform analysis on the related information by using a method such as principal component analysis or cluster analysis in addition to text mining. Further, the operator may specify a specific character string based on his / her knowledge or the like, and generate the group code PARE based on the specific character string, without performing the analysis by the related information analysis unit 129. . Further, even without the involvement of an operator, for example, using the artificial intelligence (AI), each of the processing units 122 to 128 activates the related information analysis unit 129 and the group code generation unit 12A to generate and generate the group code PARE. The association with the corresponding plant information may be performed automatically.

According to the plant equipment information management system described above, when a plurality of plants are managed, the load of input of plant information by an operator is reduced, and desired plant information is searched, extracted, and compared with high accuracy. Can be. Further, it is possible to search, extract, and compare plant information including a specific character string in the related information by using the related information accumulated with the operation of the plant.

Reference Signs List 10 Plant equipment information management system 11 Input / output unit 12 Business application unit 120 Maintenance code generation unit 121 Customer ledger creation unit 122 Process table creation unit 123 Estimation creation unit 124 Construction specification creation unit 125 Construction report creation unit 126 Construction daily report Creation unit 127 Maintenance history creation unit 128 Maintenance plan creation unit 129 Related information analysis unit 12A Group code generation unit 13 Storage unit 131 Customer BOM / WBSDB
132 Construction Schedule DB
133 Quotation DB
134 Order Cost DB
135 Equipment inspection / measurement record DB
136 Construction results DB
137 Construction History DB
138 Future Construction Plan DB

Claims (4)

1. Device information of a plurality of plants is managed by a BOM, device codes respectively corresponding to the device information input corresponding to a plurality of layers of the BOM are set, and work information to be performed on the plant is managed by a WBS. And a work equipment information management system in which work codes respectively corresponding to the work information input corresponding to a plurality of layers of the WBS are set,
   Among the plurality of layers of the BOM, the device code corresponding to the device information of the lowest layer among the layers in which the device information is always input in all of the plurality of plants, and the plurality of layers of the WBS. A maintenance code generation unit configured to generate a maintenance code corresponding only to the work code corresponding to the work information of the WBS layer directly linked to the device information of the lowest layer;
   Using the maintenance code and the device information and the work information corresponding to the maintenance code, a business application that executes a process related to the management work of the plant,
   A related information analysis unit that analyzes a character string of related information corresponding to the device information and the work information,
   A group code generation unit that generates a group code corresponding to a specific character string among the character strings;
   Has,
   A plant equipment information management system, wherein the business application extracts and displays the equipment information and the work information of the plurality of plants corresponding to the same maintenance code or the same group code.
2. After the business application displays the device information and the work information of the plurality of plants corresponding to the same maintenance code,
   The group code generating unit generates the group code based on the specific character string included in the related information corresponding to the displayed device information and the work information,
   The plant equipment information management system according to claim 1, wherein:
3. The plant equipment information management system according to claim 2, wherein the analysis is a text mining analysis.
4. The maintenance code, the group code, and a database that stores the device information and the work information corresponding to the maintenance code,
   The database includes a first database and a second database,
   The business application is a first business application that obtains first work information by executing a process related to the first work, and a second business application that obtains second work information by executing a process related to a second work different from the first work With
   The first business application stores the first work information in the first database in addition to the device information and the work information,
   The second business application copies the maintenance code, the group code, the device information, the work information, and the first work information stored in the first database to the second database, and relates to the second work. Executing a process, storing the second work information in the second database in association with the maintenance code,
   The plant equipment information management system according to any one of claims 1 to 3, wherein:

Images