JPH0877270A - Maintenance result report generation system - Google Patents

Abstract

PURPOSE: To provide the maintenance result report generation system which has the maintenance result judgement of a maintenance object equipment-the generation of a report automated on the basis of code data and document data. CONSTITUTION: Plural code data and document data showing the contents of a fault phenomenon, cause, and measures included in field operation records are stored in a data file 31 from a data input device 2. A data decoding process part 12 collates with a combination pattern of the code data with a specific rough classification rule, makes rough classifications to narrow down a decoding range, and then collates the document data with a specific small classification rule to specify small classification data. A fixed form sentence extraction part 13 extracts a fixed form sentence and a necessary supplementary sentence from the fixed form a sentence file 32 when the small classification data are specified. A report editing part 14 allocates and edits the fixed form sentence and supplementary sentence and outputs them to an output device 4, thereby obtaining the maintenance result report.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a maintenance result report creating system for automatically creating a maintenance result report to be submitted to a maintenance contractor of a device subject to maintenance, for example, after a failure countermeasure work on the device. .

[0002]

2. Description of the Related Art Conventionally, when trouble-shooting work has been carried out on a maintenance target device, a maintenance staff creates a field work record expressed by predetermined code data and sentences, and takes it back to a maintenance center for maintenance. An employee or other technician deciphers this field work record, creates the necessary diagnostic report and submits it to the equipment maintenance contractor. When preparing such a diagnostic result report, we must manually judge the failure event or failure site and
After considering the diagnosis result sentence, a sentence was input at a predetermined position in the report format using a sentence preparation device such as a word processor or a personal computer, and this was printed to produce the report.

[0003]

As described above, in the past, the contents of the field work record were manually deciphered to identify the failure event or the failure site, so that a technician skilled in the equipment is required at all times. There was a problem that had to be deployed. Moreover, since the judgment is made based on the experience of each engineer, there is a problem that the judgment result varies depending on the skill of each engineer, and the diagnosis results cannot be unified. Furthermore,
There is also a problem that a considerable amount of processing time is required because the subsequent manual input of variable diagnostic result texts, allocation thereof, text combination, editing, etc. are involved in the preparation of subsequent reports. These problems have been aggravated as the types of maintenance target devices have increased, and improvements have been desired.

In view of the above problems, an object of the present invention is to provide a maintenance result report preparation system which automates from the judgment of the maintenance result to the preparation of the report based on the code data and the text data.

[0005]

In order to achieve the above object, according to one aspect of the present invention, a plurality of pieces of code data including a type of a maintenance target device, a maintenance item, and a characteristic of a maintenance content that are input are expressed. A system for creating a maintenance result report, based on a plurality of text data, while deriving large classification data by collating a combination pattern of the input code data with a large classification rule prepared in advance, Data decoding means for identifying the small classification data related to the derived large classification data by collating the input combination pattern of the text data with a prepared small classification rule, and maintenance corresponding to the specified small classification data. There is provided a maintenance result report preparation system having an editing means for allocating a result fixed phrase to a predetermined position of a report format prepared in advance.

Preferably, the editing means reads a supplemental fixed phrase related to the small classification data from a fixed phrase file and edits it together with the maintenance result fixed phrase, and a fixed form from the report format. An area detection unit for detecting a sentence empty area is provided, and each fixed sentence is allocated to the detected empty area.

An output device for outputting the report edited by the editing means may be provided.

[0008]

[Function] The code data included in the field work record is usually limited in type and data length in consideration of the trouble of code selection when there are many types of maintenance target devices. Also has a configuration in which specific part names, function names, states thereof, etc. are connected in a predetermined order, and thus, in each case, a decoding rule can be formed by a combination of logical sum / logical product. Therefore, according to the present invention, a major classification rule that associates a combination pattern of a plurality of code data including a type of maintenance target device and a maintenance item with predetermined major classification data in advance, a combination pattern of a plurality of text data, and a minor classification data. Prepare small classification rules that correspond to and.

Then, the code data input by the data input means is collated with the large classification rule, rough classification is performed to narrow the decoding range, and then the input sentence data is collated with the small classification rule to be the small classification data. Specify. Since the maintenance result fixed phrase is associated with each small classification data, it is also possible to acquire the fixed phrase corresponding to when the small classification data is specified. The editing means allocates the small classification data and the fixed phrase to a predetermined position of the report format, for example, to an empty area detected by the area detection means, and edits them. For example, connect immediately after the maintenance result boilerplate. This is output to an output device to obtain a maintenance result report.

[0010]

Embodiments of the present invention will be described below in detail with reference to the drawings.

FIG. 1 is a block diagram showing a case in which the maintenance result report preparation system of the present invention is applied to the preparation of a diagnosis result report when a failure occurs. In this embodiment, the failure event and the failure part are automatically specified based on the code data and the text data representing the failure phenomenon, the cause, and the content of the countermeasure included in the field work record, and the corresponding fixed phrase is predeterminedly reported. Create a diagnosis result report by allocating it in the document format.

In FIG. 1, reference numeral 1 is a central processing unit, 2
Is a data input device, 3 is a storage device, and 4 is an output device such as a printer. The storage device 3 has a data file 31, a fixed phrase file 32, and a rule file 33, and the fixed sentence file 32 stores the diagnosis result fixed sentence and the supplementary sentence in advance. Further, the rule file 33 stores code data rules and text data rules used for data decoding, allocation / edit rules used for report editing, and other rules.

The contents stored in the data file 31 are as shown in FIG. 3, for example. Kn (n: 1,
, ...) are device name codes, An to Fn are symbol codes, and Gn to Nn are words or phrases. The device name code Kn and the symbol codes An to Fn are, for example, A001.
1, E0001, etc. are defined in advance by symbols such as numbers and letters. Further, Gn to Nn are text data such as words and simple sentences used by the maintenance personnel to express the findings about the equipment, which are picked up from past findings and accumulated. The present inventor analyzed past records of this type of finding and found that this type of finding is often a word or a word such as "head read failure" or "record paper feed failure". I also found out that this is done by enumerating technical terms. Therefore, these terms and the like (keywords) are accumulated by using the character code expressing them.

The symbol code can be considered as a signal itself that directly expresses the state of the device. Further, since the sentence data is a simple expression of an abnormality or failure of the device, the simple expression corresponds to enumeration of technical terms, and can be said to correspond to a character expression of a signal. For example, the above-mentioned "head read failure"
Describes the physical state of the head. Therefore, it can be said that the symbol code and the text data indicate the technical characteristics of the device.

The rule file 33 includes, for example, FIG.
Code data rules and sentence data rules as shown in (a) and (b) are stored. The code data rule and the text data rule are expressed as rules for specifying the failure event and the failure site by logically combining the data indicating the physical and / or technical characteristics of the device as described above. It is a thing. This rule is derived based on the causal relationship of each event based on past data. Therefore, these rules describe the causal relationship between the phenomenon occurring in the device and the failure event and the failure site based on the physical or technical property of the device. Examples of the contents of these code data rule and text data rule are shown in FIGS. 4 (a) and 4 (b), respectively. The former is used to roughly narrow down the decryption range, and the latter is used to identify specific events.

In the rule file 33, for example,
The allocation / editing rule and other rules as shown in FIGS. 5A and 5B and FIGS. 6A and 6B are stored.
In FIG. 5A, the identified failure event R1 and failure site S1, and pointers T1 and T2 indicating the storage addresses in the standard text file 32 of the diagnostic result standard text corresponding to them.
And the number of lines X1 and X2, and supplementary sentence numbers Y1 and Y2 are shown. In FIG. 5B, the supplementary sentence numbers Y1 and Y2 and the pointers I1 and I2 indicating the storage addresses of the actual supplementary sentence in the standard sentence file 32 and the number of lines L are shown.
The correspondence between 1 and L2 is shown. Further, FIG. 6A shows an example of the sentence combination rule, and FIG. 6B shows an example of the allocation rule.

The central processing unit 1 has an I / O control unit 11 for controlling the input / output of data with the data input device 2, the output device 4 or the storage device 3, and a failure based on the code data and the text data. A data decoding processing unit 13 that identifies an event / failure part, a fixed sentence extraction unit 13 that extracts a diagnostic result fixed phrase and a necessary supplemental sentence corresponding to the specified failure event / failure region, and the extracted fixed phrase and supplemental sentence Is assigned to a predetermined position of the report format and is output to the output device 4.

The data input device 2, as shown in FIG.
This is a device that has at least a keyboard 21 and a storage device 22, and a central processing unit and a display device, which are not shown, and is capable of inputting code data and text data as described below by itself. That is, it is composed of a small computer system having a simple word processor function. The data input device 2 is connected to the central processing unit 1,
It is for transferring the data to the central processing unit 1 by the input stored in the storage device 22 and inputting the data. In this data input device 2, for example, a data input format as shown in FIG. 9 is prepared in advance, and a maintenance staff inputs the necessary data to this in order. The data input format shown in FIG. 9 may prompt the maintenance personnel to input necessary data by displaying the formats partially sequentially on the display screen of a display device (not shown) according to the input order. it can.

Next, referring to FIGS. 2 to 8, the processing procedure of the diagnostic result report creating system having the above-mentioned configuration will be described together with the operation contents of each section.

FIG. 2 is an overall processing procedure diagram, and S represents a processing step.

In this system, first, the code data and the text data input from the data input device 2 are stored in the data file 31 according to the field work record (S (processing step, the same applies hereinafter) 100).

In the data decoding processing unit 12, the code data and the text data, the corresponding code data rule and the corresponding text data rule are read into the work area,
The failure event and the failure site are specified by comparing and judging the both. Specifically, as shown in FIG. 4, first,
The logical condition of the code data rule and the combination pattern of the code data are compared, and if they match, the event major classification name and the fault site major classification name are derived according to the code data rule (S101). For text data,
For each major classification, the keywords (words,
A matching pattern of the same keywords in the sentence data is searched for in accordance with the logical condition (for example, clause), and if they match, the failure event and the failure part according to the rule are specified (S1).
02). In this way, the failure event and the failure part are automatically identified (decoded).

In the standard sentence extraction unit 13, the standard sentence specified by the rule file shown in FIG. 5A is converted into the standard sentence file 32 by using the specified fault event and fault site as keys.
Read out from this and use this as the diagnostic result sentence (S10).
2). For example, when the specified failure event is R1 and the failure part is S1, as shown in FIG. 5 (b), a pointer T for storing the diagnostic result standard sentence corresponding to these
1, T2, the number of lines X1, X2, and supplemental sentence number Y
1 and Y2 are obtained. In this example, since the supplementary sentence exists, the fixed sentence extraction unit 13 uses the supplemental sentence numbers Y1 and Y2 as keys to extract the corresponding supplementary sentence I1 from the fixed sentence file 32.
I2, L1, and L2 are also read (S103).

In the report text editor 14, the rule file 3
6 and the sentence combination rule of FIG. 6A extracted from FIG.
According to the allocation rule of (b), the diagnosis result standard sentence and the supplemental sentence are allocated / edited (S105). At this time, it is advisable to detect an empty area in the report format using a known area detection method and perform the allocation / editing on the detected empty area. After that, the edited data is output to the output device 4 together with the required print control signal and printed out to obtain a diagnostic result report (S106).

FIG. 7 is an explanatory diagram of the contents of the code data and the sentence data based on a specific failure case, and the underline of the sentence data shows the keyword to be compared with the sentence data rule. FIG. 8 shows an example of the code data rule, the sentence data rule based on this case, and the corresponding fixed-form sentence specified by these rules. That is, in this example, as shown in FIG. 7, the model name “WP-1”, the device name “ABC10”, and the phenomenon code “A”.
_“1 · B ₁ ”, the cause code “C ₁ · D ₁ ”, and the countermeasure code “E ₁ · F ₁ ” are entered as codes. On the other hand, as shown in FIG. 8, a CRT, a display, etc. are input as the text indicating the phenomenon, a CRT, a control unit, etc. are input as the text indicating the cause, and adjustment is impossible, CRT replacement, etc. as the text indicating the countermeasure. Has been entered. In the example sentence shown in FIG.
A word without underline indicates a word that is not registered in the rule. In the case of this embodiment, unregistered words are ignored, and the rule is applied based on the registered words.

When such a code and a sentence are input, first, the code data rule is applied to the code data, and the event major category of "control unit defect of display device (CRT unit)" is specified. Further, by applying the sentence data rule to the sentence data, the small classification event “display device“ CRT unit ”under the large classification is applied.
The phenomenon "defective display character distortion due to defective deflection circuit" is introduced. Then, along with this phenomenon, the prepared sentence and supplementary sentence prepared in advance are read from the fixed sentence file and output. As the fixed sentence and the supplementary sentence, for example, the following report sentence is automatically output. That is, "The display deflection circuit was defective, and the control circuit and cathode ray tube were replaced. Also, please be aware that the same phenomenon may occur if there is a strong magnetic device nearby. In addition, it is a free period until November 1994,
After that, we will charge you. A report such as "is automatically created.

As is clear from these examples, the diagnostic result report preparation system of this embodiment decodes the contents written in the field work record based on the combination pattern of the code data and the combination pattern of the text data. However, since the diagnosis result report is created, it is possible to automate a series of work contents, and it is possible to prevent mistakes due to human data input as in the past. Further, since there is no variation in judgment due to the difference in technical ability between maintenance personnel and technicians, the diagnosis results can be made uniform.

It should be noted that the present invention can be widely applied to all record / report data including code data and text data, in addition to the preparation of a diagnostic result report at the time of failure based on the field work record. Is.

[0029]

As is apparent from the above description, according to the maintenance result report preparation system of the present invention, the large classification data is derived from the combination pattern of the code data by the comparison judgment with the predetermined rule, Furthermore, since the small classification data related to the large classification data is specified from the combination pattern of the text data, the content of the combination pattern of each data can be easily and quickly specified. Further, by preliminarily associating the small classification data with the fixed text representing the maintenance result and the necessary supplementary text, it becomes possible to extract the fixed text and the supplementary text when the small classification data is specified. Complete automation from decryption to report editing and output is possible. As a result, it is possible to solve all the problems in the related art due to the manual judgment of the maintenance result, the input of the sentence based on the judgment result, and the editing of the report.

[Brief description of drawings]

FIG. 1 is a configuration diagram of a maintenance result report creating system according to an embodiment of the present invention.

FIG. 2 is an overall processing procedure diagram of the system of this embodiment.

FIG. 3 is an explanatory diagram showing an example of contents of code data and text data stored in a data file in this embodiment.

FIG. 4A is an explanatory diagram showing an example of code data rules stored in a rule file and FIG. 4B is an example of sentence data rules in this embodiment.

FIG. 5A is an explanatory diagram of a correspondence relationship between a specified failure event / region and a diagnostic result standard text; and FIG. 5B is an explanatory diagram of a correspondence relationship between the diagnostic result standard text and a supplemental text.

FIG. 6A is an explanatory diagram showing an example of a sentence combination rule, and FIG. 6B is an explanatory diagram showing an example of an allocation rule.

FIG. 7 is an explanatory diagram of contents of specific code data and text data.

8 is an explanatory diagram showing an example of a code data rule, a sentence data rule based on the case of FIG. 7, and a fixed phrase narrowed down according to each rule.

FIG. 9 is an explanatory diagram showing an example of a data input format of the data input device.

[Explanation of symbols]

 1 central processing unit 11 I / O control unit 12 data decoding processing unit 13 fixed sentence extraction unit 14 report editing unit 2 data input device 3 storage device 31 data file 32 fixed sentence file 33 rule file 4 output device

─────────────────────────────────────────────────── ─── Continuation of the front page (51) Int.Cl. ⁶ Identification code Internal reference number FI Technical display location G06F 17/30 9194-5L G06F 15/401 310 D (72) Inventor Tatsuya Saito Within Chiyoda-ku, Tokyo 2-14-6, Kanda, inside of Ritsuden Electronic Service Co., Ltd.

Claims (7)

[Claims] 1. A system for creating a maintenance result report based on a plurality of inputted code data including a type of maintenance target equipment, a plurality of maintenance items and a plurality of text data representing characteristics of maintenance contents. Then, the combination pattern of the input code data is collated with a large classification rule prepared in advance to derive predetermined large classification data, and the combination pattern of the input text data is prepared in advance with a small classification rule. Data decoding means for identifying the small classification data related to the derived large classification data by collating with the above, and allocating the maintenance result fixed phrase corresponding to the specified small classification data to a predetermined position of a report format prepared in advance A maintenance result report preparation system characterized by having means and. 2. The maintenance result report creation system according to claim 1, wherein the editing unit reads a supplementary fixed phrase related to the small classification data from the fixed phrase file and edits it together with the fixed maintenance result fixed phrase. A maintenance result report preparation system comprising sentence connection means. 3. The maintenance result report creating system according to claim 1, wherein the editing means has area detecting means for detecting a blank area of a fixed phrase from the report format, and each of the detected empty areas has an area detecting means. A maintenance result report creation system characterized by being configured to allocate fixed phrases. 4. The maintenance result report creating system according to claim 3, further comprising an output device for outputting the report edited by the editing means. 5. The maintenance result report preparation system according to claim 1, 2, 3 or 4, further comprising a storage means for storing the large classification rule, the small classification rule and the report format in advance. The data decoding means reads the large classification rule and the small classification rule from the storage means to perform the matching, and the editing means uses the report format read from the storage means. Calligraphy system. 6. A system for creating a maintenance result report based on a type of maintenance target equipment, a plurality of code data including a maintenance item, and a plurality of text data representing characteristics of maintenance content, which is a maintenance target. A data input device for inputting a plurality of code data including a device type and a maintenance item, and a plurality of text data indicating a feature of maintenance content, and a plurality including a type of a maintenance target device and a maintenance item from the data input device A central processing unit that takes in a plurality of text data representing the characteristics of the code data and maintenance content, applies a prepared rule, and creates a maintenance result report based on a prepared sentence, A storage device for storing a prepared rule and a fixed phrase used when the central processing unit creates a report, and a report created by the central processing unit And an output device 4 for outputting, the storage device as a rule, a large classification rule for specifying a large classification of events based on a combination pattern of the input code data, and the input sentence The sub-classification data for specifying the sub-classification data of the event based on the combination pattern of the data is stored, and the central processing unit stores the input combination pattern of the code data in the storage unit. The predetermined large classification data is derived by collating with the large classification rule, and the combination pattern of the input sentence data is collated with the small classification rule stored in the storage device to the derived large classification data. Data decryption means for identifying related sub-classification data and maintenance result boilerplate corresponding to the identified sub-classification data are stored from the storage device. Read a report format has, maintenance results reporting system characterized by having an editing means for assigning a predetermined position of the report format. 7. The maintenance result report preparation system according to claim 6, wherein a plurality of data input devices are prepared.