WO2003105039A1 - トラブル対処支援システムおよびこれに接続される端末装置 - Google Patents
トラブル対処支援システムおよびこれに接続される端末装置 Download PDFInfo
- Publication number
- WO2003105039A1 WO2003105039A1 PCT/JP2003/007174 JP0307174W WO03105039A1 WO 2003105039 A1 WO2003105039 A1 WO 2003105039A1 JP 0307174 W JP0307174 W JP 0307174W WO 03105039 A1 WO03105039 A1 WO 03105039A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- judgment
- procedure
- support system
- trouble
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
- G05B23/0267—Fault communication, e.g. human machine interface [HMI]
- G05B23/027—Alarm generation, e.g. communication protocol; Forms of alarm
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
- G05B23/0275—Fault isolation and identification, e.g. classify fault; estimate cause or root of failure
- G05B23/0278—Qualitative, e.g. if-then rules; Fuzzy logic; Lookup tables; Symptomatic search; FMEA
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0748—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a remote unit communicating with a single-box computer node experiencing an error/fault
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2294—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing by remote test
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2223/00—Indexing scheme associated with group G05B23/00
- G05B2223/06—Remote monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
Definitions
- the present invention relates to a monitoring system that remotely monitors various devices such as a clinical test device via a communication network and predicts a failure of the device.
- a troubleshooting manual or service manual (hereinafter simply referred to as a manual) is used to identify the cause of the failure and the repair method based on the failure symptoms.
- a manual a troubleshooting manual or service manual
- items for finding the cause of failure are arranged in an appropriate order in the manual. For example, for a failure symptom, the most frequent cause of this symptom is listed earlier in the manual reference order, so that the user or service engineer of the equipment can find the cause of the failure. The time required for repair can be shortened, and quick recovery can be achieved.
- the manual be described so that the most probable cause of the failure that can be inferred from the failure symptom and the effective repair procedure for the failure cause are allocated preferentially.
- manuals not described in this way have the problem that it takes time to identify the cause of the failure. For example, check items that are not directly related to the cause of failure are listed in the manual with priority.However, if the checking procedure is complicated and time-consuming, many service engineers Consider using this manual for repairs Then, the loss of time as a whole cannot be ignored.
- the present invention in order to solve this problem, realizes a trouble handling support system that can efficiently identify the cause of a failure and can provide an online manual that does not require revision work. With the goal.
- the troubleshooting support system of the present invention provides a list of event data of a trouble that can occur in the device, a list of judgment material data for identifying the cause of the event, and And a judgment route storage means for storing a list of coping procedure data together with the correlation between these data, and when event data is inputted, judgment material data relating to the event is extracted from the judgment route storage means.
- a judgment route storage means for storing a list of coping procedure data together with the correlation between these data, and when event data is inputted, judgment material data relating to the event is extracted from the judgment route storage means.
- the “fitness” of the judgment material means the number of times and frequency at which the judgment material was decisive in identifying the cause of an event.
- the judgment material data is stored in accordance with the degree of conformity means that the judgment material data is stored together with the numerical data of the degree of conformity, and that the judgment material data is stored in the storage area. Includes both forms arranged in order according to degree. '
- the apparatus further includes a fitness determination unit that performs a process of determining
- the degree of conformity of the judgment material data with respect to each of the event data is determined according to the number or frequency of selection of each judgment material data in the trouble case stored in the result storage means. Maintenance will be performed automatically so that a response procedure according to the conformity of the judgment data is presented without the need for revision.
- a data for determining a priority of the troubleshooting procedure data for each cause is further stored in the determination route storage means, and the troubleshooting procedure presenting means includes: Present the coping procedure data extracted from the judgment route storage means according to the priority. Is preferred.
- the time required for each coping procedure, the cost required to execute each coping procedure, or the same event occurs due to the same cause in the same device after executing each coping procedure It is preferable that at least one of the following averages is stored in the judgment route storage means.
- a configuration may be used in which the user selects and inputs which data is to be used to determine the priority based on at least two types of time until the same event occurs due to the same cause in the same device.
- the handling procedure data includes an action content describing each action.
- an input unit for selecting or arbitrarily inputting a combination of the event data, the judgment material data, and the coping procedure data; and the event data, the judgment material data, and the input by the input unit.
- the apparatus further comprises a new route registering means for storing the coping procedure data in the determination route storage means in association with each other.
- a terminal device is a terminal device connected to any of the above-described troubleshooting support systems, and allows input of event data of a trouble occurring in the device.
- a response procedure display means for receiving the response procedure data output by the response procedure presentation means and displaying the received response procedure data.
- FIG. 1 is a block diagram showing a schematic configuration of a service support system and an SE terminal according to an embodiment of the present invention.
- 2 (a) to 2 (d) are explanatory diagrams showing an example of data stored in the service support system.
- FIGS. 3A and 3B are explanatory diagrams showing an example of data stored in the service support system.
- Fig. 4 shows an example of the screen displayed when the SE terminal connects to the service support system.
- Fig. 5 is an example of the symptom selection screen displayed on the SE terminal by the service support system.
- Fig. 6 is an example of the judgment material selection screen displayed on the SE terminal by the service support system.
- FIG. 7 is an example of a coping procedure selection screen displayed on the SE terminal by the service support system.
- FIG. 8 is an example of an action list screen displayed on the SE terminal by the service support system.
- FIG. 9 is an example of an action explanation screen displayed on the SE terminal by the service support system.
- FIG. 10 is an example of a repair report input screen.
- Figure 11 shows an example of a repair report input screen when a service engineer registers a new route.
- Figure 12 is an example of the screen displayed on the SE terminal after the screen in Figure 11 when the service engineer registers a new route.
- FIG. 13 is an example of a screen displayed on the SE terminal after the screen of FIG.
- FIG. 14 is an example of a screen displayed on the SE terminal after the screen of FIG.
- FIG. 15 is an example of a screen displayed on the SE terminal after the screen of FIG.
- FIG. 16 is an example of a screen displayed on the SE terminal after the screen of FIG.
- FIG. 17 is a block diagram showing a schematic configuration of the SE terminal. BEST MODE FOR CARRYING OUT THE INVENTION
- the service support system according to the present embodiment is a system that is operated and managed by a device maker in order to support a service engineer who repairs and maintains a device delivered to a user (hereinafter, referred to as a user device). .
- the service support system 1 of the present embodiment is connected to the SE terminal P l 5 P 2- (hereinafter referred to as the SE terminal P) carried by the service engineer via the Internet 30. ).
- the SE terminal P can be realized by any portable terminal that can be connected to the Internet every day, such as a personal computer, a PDA, or a portable telephone.
- the service engineer connects to the service support system 1 via the Internet 30 using the carried SE terminal P, and from the service support system 1 to the SE terminal P. Work according to the online manual provided to
- the service engineer first inputs the symptom of the failure of the user equipment to the SE terminal P. Even if the symptoms of a failure are the same, the causes often vary, so it is important to correctly and promptly identify the cause of the failure in order to correct the failure properly and efficiently.
- the service support system 1 associates, for each conceivable failure, a symptom, its cause, and a judgment material for identifying a cause from the symptom with a database. I remember. Then, when the service engineer inputs symptoms from the SE terminal P, the service support system 1 searches the database for possible judgment materials considered to be effective for identifying the cause in accordance with the input symptoms. Select and display on the display of SE terminal P in appropriate priority. The priority (degree of conformity) of this judgment material will be described in detail later, but is determined in the service support system 1 based on the accumulation of failure handling cases, and will be appropriately determined as new response cases are accumulated. It will be updated.
- the service engineer identifies the cause of the failure by checking the judgment information displayed on the SE terminal P in descending order of priority.
- the service support system 1 selects a description of a coping method corresponding to the cause from the database, and displays the explanation on the display of the SE terminal device P with an appropriate priority. As a result, the service engineer can proceed with the work while watching the explanation displayed on the display of the SE terminal P, so that the repair or maintenance work can be performed appropriately and efficiently.
- the service engineer After performing repair work, the service engineer creates a repair report on the SE terminal P.
- This report may include, for example, information about the user (user name, etc.), information about the failed user device (model name, Device ID, etc.), information on the symptoms of the failure, the judgment factors that helped to determine the cause, and the action to be taken, etc. are input.
- the information input to the repair report by the service engineer is sent from the SE terminal P to the service support system 1. Based on the information, the service support system updates the database storing the above-mentioned judgment materials, and updates the priorities of the judgment materials and coping procedures.
- the service support system 1 has a coping procedure-action data storage unit 11, an action data storage unit 12, a content storage unit 13, and a repair report data storage unit 14 ( (Storage means), evaluation data storage unit 15, judgment route data storage unit 16 (judgment route storage unit), cause-coping procedure correspondence data storage unit 17, user device information master 18 etc.
- Storage means Storage means
- evaluation data storage unit 15 evaluation data storage unit
- judgment route data storage unit 16 judgment route storage unit
- cause-coping procedure correspondence data storage unit 17 user device information master 18 etc.
- the communication processing unit 19 From the data storage unit 10, the communication processing unit 19, the data extraction unit 20 (judgment material presenting means, coping procedure presenting means), the update processing unit 21 (conformity determining means, new route registration means), etc. Be composed.
- the data extraction unit 20 judgment material presenting means, coping procedure presenting means
- update processing unit 21 conformity determining means, new route registration means
- the action response data storage unit 11 stores, for each user device model, a code for the troubleshooting procedure and one or more The action code is recorded in an associated state.
- An action is a unit of work performed by a service engineer, such as “confirm...”, “exchange...”, “adjust...”.
- Each action is not necessarily composed of a single action, and may include a series of actions.
- the action of “replacing a seal” includes not only an operation of replacing a seal, but also an ancillary operation such as “remove a cover (of a seal part to be replaced)”.
- the HA-811 SR0302 which is one of the handling procedures, is composed of four functions A011, A239, A021, and AO12.
- the action data storage unit 12 stores the action number, the time required for each action, and the parts price required for each action for all the actions related to each user device.
- the hyperlink to the action content corresponding to each action is recorded in an associated state.
- the action content is content for displaying a detailed description of the action on the SE terminal P so that the service engineer can refer to the content during the repair work.
- the content storage unit is provided as a file in an HTML format or the like. Recorded in 13.
- the repair report data storage unit 14 stores the data of the repair report created by each service engineer after completion of the work, that is, the report number, the model name of the user equipment that has been repaired.
- the device ID of the user device The device ID of the user device, the work date, the code of the failure symptom, the code of the judgment material that was the decisive factor for identifying the cause, the code of the identified failure cause, the code of the handling procedure referenced during the repair work, etc. It is recorded in a state of being linked to each other.
- the evaluation data storage unit 15 stores the cause-based MTBF, MTB F, calculation completion report number, and 'MTTR, cost, etc. are recorded.
- MTB F means the average value of the time from the occurrence of one failure to the occurrence of the next failure, but the ⁇ cause-based MTB F '' is different from the normal MTBF, and is different from the normal MTBF. It shows the average value of the time until a failure due to the same cause occurs again.
- the data stored in the evaluation data storage unit 15 will be described later in detail, but is appropriately updated by the update processing unit 21 based on the contents of the repair report data storage unit 14. As shown in Fig.
- the judgment route data storage unit 16 (judgment route storage unit) is specified from the combination of the symptom code and judgment material code, and the symptom and judgment material for each user device model. It stores the relationship with the cause code. For example, in the example shown in Fig. 3 (a), if the symptom code is "T11" in HA-811 (H ⁇ , if "J23" is selected The cause code of the failure is specified as “R 01.” The records in the judgment route data storage unit 16 are sorted in the order of the model name, and the records with the same model name are further identified by the symptom code.
- records with the same symptom code are sorted in order of the number of records used to identify the cause of the symptom, in which the code for the same symptom code is used.
- the judgment that was most frequently used as a decisive factor to identify the cause in past repair cases The material is "J2 3", followed by "J02"
- the order of the judgment material code in the judgment route data storage unit 16 is determined by the update processing unit 21 based on the data stored in the repair report data storage unit 14 as described later. It is updated at the timing of.
- the cause-one handling procedure correspondence data storage unit 17 stores the relationship between the cause code and the handling procedure code for each user device model. For example, in the example of Fig. 3 (b), if the cause of the trouble is identified as "R02" in HA-8180, "SR0302", " There are four types, "SR0201”, “SR0408”, and "SR0409".
- the communication processing unit 19 controls communication with an external device such as the SE terminal P via the Internet 30.
- the data extraction unit 20 (judgment material presentation unit and response procedure presentation unit) extracts data from each unit of the data storage unit 10 according to given conditions.
- the update processing unit 21 performs a process of updating the priority of the judgment material and the like.
- the operation of the service support system 1 and the SE terminal P will be specifically described by taking as an example a case where a certain user device (model name: HA-8160) has failed.
- the service engineer When the service engineer arrives at the user after being contacted by the device user, the service engineer connects to the service support system 1 via the Internet 30 from the SE terminal P. As a result, a screen for selecting and inputting the model name of the user equipment (model selection screen) is displayed on the display of the SE terminal P, for example, as shown in FIG.
- the selected model code is transmitted to the data processing unit 19 via the communication processing unit 19 of the service support system 1. It is sent to the extraction unit 20.
- the data extracting unit 20 stores the contents of a screen (symptom selection screen) for selecting and inputting a symptom from a list of troubles assumed for the model, for example, as shown in FIG. Extract from The extracted content is passed to the communication processing unit 19 and sent to the SE terminal P.
- a screen as shown in FIG. 5 is displayed on the display of the SE terminal P.
- the service engineer selects the symptom corresponding to the symptom of the user device on the symptom selection screen displayed on the SE terminal.
- the user device to be repaired is called “Til Low Flow Rate”. It is assumed that a trouble message is displayed and that the service engineer has selected "T1 1 " on the symptom selection screen as shown in Fig.5.
- the codes (DX x, EX x, T xx, etc.) shown at the beginning of each symptom on this screen are the symptom codes that are uniquely assigned to each trouble symptom. When selected, this symptom code is transmitted from the S ⁇ terminal ⁇ to the service support system 1.
- the data extraction unit 20 uses the received symptom code as a key to store the judgment route data storage unit 16 Refer to and extract a judgment material code to identify the cause of the symptom.
- the judgment route data storage section 16 stores judgment materials for identifying the cause of each symptom in the order of the number of times that the cause of identifying the cause in a past repair case was determined. ing.
- the data extraction unit 20 transmits the judgment material code extracted from the judgment route data storage unit 16 to the S ⁇ terminal ⁇ according to the priority. As a result, as shown in Fig.
- a screen for determining the cause of the failure based on the symptoms and displaying the screen in a prioritized manner is displayed on the display of the SE terminal ⁇ . Is done.
- judgment materials for identifying the cause of the trouble (“ ⁇ 11”) are displayed with priorities ( ⁇ .1 ⁇ ).
- the code (Jxx) shown after the priority is the judgment material code uniquely assigned to each judgment material.
- the service engineer checks the judgment materials (items to be confirmed) displayed on this judgment material selection screen in descending order of priority. That is, in the example of FIG. 6, first, check whether there is any liquid leakage from the injection valve (No. 1 J23). Check if air bubbles are generated in the air (No. 2 J 02). Here, if it is determined that bubbles are generated, the service engineer selects this confirmation item (No. 2 J02) on the judgment material selection screen. As a result, the selected judgment material code is transmitted from the SE terminal P to the service support system 1.
- the data extracting unit 20 upon receiving the judgment material code transmitted from the SE terminal P, uses the model name of the user equipment, the symptom code, and the judgment material code as keys to make a judgment route data storage unit. Identify the cause by referring to 16. For example, in the above case, assuming that data as shown in FIG. 3A is stored in the judgment route data storage unit 16, the model name is "HA-8180" and the symptom code is " The cause code identified is "R02" because T11 is "J02".
- the data extraction unit 20 refers to the cause-one-response-procedure correspondence data storage unit 17 based on the cause code, and extracts a response procedure for dealing with the cause. For example, if the content of the cause-one-response-procedure correspondence data storage unit 17 is data as shown in Fig. 3 (b), and if the cause code is "R02", "SR030 Four types of "2", “SR0201”, “SR0408”, and "SR0409" are extracted. The data extracting unit 20 further extracts information on actions constituting each of the extracted coping procedures from the coping procedure-action coping data storage unit 11 and the action data storage unit 12.
- the data extraction unit 20 further extracts each MTTR of the extracted coping procedure from the evaluation data overnight storage unit 15. Then, the data extracting unit 20 assigns priorities to the extracted coping procedures in ascending order of the value of MTTR and transmits the same to the SE terminal P. As a result, as shown in FIG. A screen (action procedure selection screen) is displayed on the ray, in which the action steps to deal with the cause "R02" are arranged in ascending order of MTTR.
- the coping procedure selection screen shows the coping procedure specified from the combination of the selected trouble event and the judgment material as described above.
- the combination of the trouble event (event code "T11") selected on the event selection screen and the judgment material (judgment material code "J02") selected on the judgment material selection screen is All the response procedures selected by the service support system 1 are displayed with priorities.
- three priorities for displaying the response procedure are as follows: (1) MTTR is short, (2) MTBF is long, and (3) repair cost is low. It is possible to select one of them.
- three countermeasures are displayed in ascending order of MTTR.
- the data extraction unit 20 According to the selection, reference is made to the evaluation data storage unit 15 to sort and display the coping procedures. Also, in this example, when the response procedure selection screen is displayed first, it is arranged in ascending order of MTTR.However, it is displayed first in MTB F order or cost order, and sorted according to the selection of the service engineer. It may be done.
- the display screen of the SE terminal P is included in the selected response procedure, for example, as shown in FIG.
- the screen changes to a list of actions to be performed.
- Each function displayed on the screen shown in Fig. 8 is linked.
- the service engineer selects an action as shown in FIG. 8
- the action content corresponding to the selected action is extracted from the content storage unit 13 by the link attached to the selected action, and the SE terminal Displayed on the screen of machine P.
- FIG. 8 JP03 / 07174
- the screen display of the SE terminal P changes to a screen as shown in FIG. 9, for example.
- the service engineer performs repair work while looking at this screen.
- the action content is configured so that the screen can be scrolled, a part of the screen can be enlarged, or the screen can be moved to the next or previous screen as needed.
- the service engineer calls a repair report creation screen as shown in Fig. 10 on the SE terminal P and inputs necessary items.
- FIG. 10 and FIGS. 11 to 16 to be described later illustration of a frame or the like of a browser is omitted.
- This screen has a route input field 40.
- "Tl1" is selected on the event selection screen of Fig. 5
- "J02” is selected on the judgment material selection screen of Fig. 6
- "SR 1" is selected on the coping procedure selection screen of Fig. 7. Since “0302” was selected, the service engineer enters these codes in the route input box 40 as shown in FIG.
- the data entered in the route entry field 40 is transmitted from the SE terminal P to the service support system 1 together with other data entered on the repair report creation screen.
- the update processing unit 21 converts the repair report data transmitted from the SE terminal P into a repair report data storage unit as shown in, for example, FIG. 2 (c). Memorize in 14.
- the priority of the judgment material in the judgment route data storage unit 16 and the evaluation data storage unit 1 are periodically determined. Update processing is performed for the various data in 5. This update process can be performed once a day or once a month, for example. 0307174
- This may be performed once every fixed period, such as once, or may be performed each time a predetermined number of new repair report data are added to the repair report data storage unit 14.
- the update processing unit 21 determines the priority of the judgment material in the judgment route data storage unit 16 based on all the repair results stored in the repair report data storage unit 14 based on the same symptom in the same model. Calculate the number of times each judgment material code is used. Then, based on the calculation result, the update processing unit 21 determines the route of the judgment in such a manner that in the past repair results, the material for the judgment of each symptom of each model is in the descending order of the number of times of determining the cause. The records are rearranged in the storage unit 16.
- the update processing unit 21 updates the contents of the evaluation data storage unit 15 based on the data stored in the repair report data storage unit 14. First, the update processing unit 21 extracts, from the record added after the previous update process, records in which the device ID, the symptom, and the cause are all the same, into the repair report data storage unit 14, and stores those records. Calculate the work day interval in the record. For example, in the example of Fig. 2 (c), the record with the report number "1 2345 6" and the record with the report number "1 2 3452" have the same device ID, symptom, and cause. Obtain the difference in the date recorded in the work date column. In this case, the difference between March 26, 2002 and March 12, 2002 is 14 days.
- the update processing unit 21 uses this value to update the value of the cause-based MTBF for the corresponding model name (HA-8160) and the corresponding action procedure (SR0302).
- the cause of the response procedure "SR0302" for HA—8161 is MTBF of 193 days.
- the number of days for the cause-based MTBF is updated to 186, the number of samples to 24, and the operation completion report number to 123452.
- the update processing unit 21 updates the priority of the judgment material and the value of the cause base MTBF at a predetermined timing.
- a service engineer can add a new route to the judgment route data storage unit 16 by the following procedure. For example, if a service engineer accesses the service support system 1 from the SE terminal P to correct a failure in a certain user device, but fails to provide appropriate information, he / she will take appropriate measures. The content of the executed work can be registered in the service support system 1.
- a warning message “T ll: Low flow rate” is displayed at a certain user device, and the service engineer accesses the service support system 1 from the SE terminal P. Is not shown.
- the service engineer examined it himself, it was found that "bubbles were generated in the solution A flow path", and the cause was "poor connection between the elution liquid tube and the back panel". I understand it.
- a service engineer will replace the seal (action code: AO11), tighten the connection between the eluent tube and back panel (A239), and check the piping pressure (AO2). It is assumed that the four actions of 1) and measurement operation confirmation (AO 1 2) are sequentially executed.
- the service engineer displays on the SE terminal P as shown in Fig. 11.
- select a symptom in the route input field 40 On the displayed repair report creation screen, select a symptom in the route input field 40.
- all warning messages output by the user devices are registered in advance in the user device information master 18 of the service support system 1, and all the warning messages are displayed in a list in the route input column 40. Therefore, the service engineer only has to select an appropriate one from the displayed warning messages.
- a new symptom code and its description may be created for a symptom that is not registered as a master.
- the service engineer inputs the symptom code and presses the "Create New" button
- the screen of the SE terminal P changes to a screen for entering the cause as shown in Fig. 12.
- the service engineer inputs the location (unit name) that caused the failure.
- select “Flow system” and press “Next” button As a result, the screen of the SE terminal P changes to a screen as shown
- the components of the flow path are extracted from the user device information box 18 and are listed in the component list column 41.
- the service engineer selects the corresponding part from the list and presses the additional button 42 in the cause location column.
- the added parts are displayed in the cause location column 43.
- the screen of the SE terminal changes to the screen shown in Fig. 14.
- the service engineer selects the cause (stress). In this case, select “poor connection”.
- the service engineer presses the “Next” button the screen of the SE terminal changes to the screen shown in Figure 15.
- the service engineer inputs a criterion for identifying the cause using an arbitrary character string.
- the criteria to be entered here are Consideration is made so as to be objectively different from the criterion. This is so that other service engineers can understand the difference in the criteria.
- the criterion input by the service engineer is "bubbles are generated in the liquid A channel".
- the screen of the SE terminal changes to the screen shown in Fig. 16.
- the service engineer inputs the contents of the work performed to repair the failure by using the action numbers "AO 1 1", "A 2 39", “AO 2 1", “AO 1 2”. .
- the information input by the service engineer is stored by the update processing unit 21 in the decision route data storage unit 16, the cause-coping procedure correspondence data storage unit 17, and the coping procedure-action correspondence data storage. Registered in Department 11 and made available to other service engineers.
- the SE terminal P is configured as an arbitrary portable terminal device that can be connected to the Internet.
- the event input support unit 51 receives the content data of the model selection screen (for example, see FIG.
- the judgment material input support unit 52 converts the content data of the judgment material selection screen (for example, see FIG. 6) Service : "Receive from service support system 1 and display it on display 54, and let the service engineer select and input one of the judgment data.
- the response procedure display section 53 is sent from the service support system 1.
- the content data of the response procedure (see, for example, FIGS. 7 to 9) is received, and the received response procedure data is displayed on the display 54.
- FIGS. 2A to 2D and FIGS. 3A and 3B show examples of data of sequential file formation.
- the data structure is not limited to sequential files.
- the judgment route data storage unit 16 is also configured such that the priorities of the judgment materials are represented by the arrangement order of the records in order, but each record has an attribute indicating the priority of the judgment materials. It may be.
- the logical configuration of the data storage unit 10 shown in the present embodiment is merely an example, and the data structure is arbitrarily changed in consideration of data retrieval efficiency and efficient use of storage capacity. It is possible.
- a troubleshooting support system that can efficiently identify the cause of a failure and that can provide an online manual that does not require revision work is realized. it can.
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Computer Hardware Design (AREA)
- Automation & Control Theory (AREA)
- Fuzzy Systems (AREA)
- Mathematical Physics (AREA)
- Human Computer Interaction (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Testing And Monitoring For Control Systems (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP03736059A EP1533730A4 (en) | 2002-06-07 | 2003-06-06 | PROBLEM SUPPORT SYSTEM AND ASSOCIATED END DEVICE DEVICE |
JP2004512040A JPWO2003105039A1 (ja) | 2002-06-07 | 2003-06-06 | トラブル対処支援システムおよびこれに接続される端末装置 |
AU2003242223A AU2003242223A1 (en) | 2002-06-07 | 2003-06-06 | Trouble countermeasure support system and terminal device connected to the same |
US10/517,162 US7050941B2 (en) | 2002-06-07 | 2003-06-06 | Trouble countermeasure support system and terminal device connected to the same |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2002-167786 | 2002-06-07 | ||
JP2002167786 | 2002-06-07 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2003105039A1 true WO2003105039A1 (ja) | 2003-12-18 |
Family
ID=29727675
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2003/007174 WO2003105039A1 (ja) | 2002-06-07 | 2003-06-06 | トラブル対処支援システムおよびこれに接続される端末装置 |
Country Status (6)
Country | Link |
---|---|
US (1) | US7050941B2 (ja) |
EP (1) | EP1533730A4 (ja) |
JP (1) | JPWO2003105039A1 (ja) |
CN (1) | CN1659561A (ja) |
AU (1) | AU2003242223A1 (ja) |
WO (1) | WO2003105039A1 (ja) |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006092183A (ja) * | 2004-09-22 | 2006-04-06 | Fuji Xerox Co Ltd | 画像形成装置の障害対処システムおよび方法 |
WO2006065328A1 (en) * | 2004-12-14 | 2006-06-22 | Snap-On Incorporated | Dynamic information method and system |
WO2006077193A1 (en) * | 2005-01-18 | 2006-07-27 | International Business Machines Corporation | History-based prioritizing of suspected components |
JP2007179535A (ja) * | 2005-11-29 | 2007-07-12 | Omron Corp | 不良対策選択装置、不良対策選択方法、不良対策選択用プログラム、および不良対策選択用プログラムを記録した記録媒体 |
WO2009150737A1 (ja) * | 2008-06-12 | 2009-12-17 | 富士通株式会社 | 保守業務支援プログラム、保守業務支援方法および保守業務支援装置 |
US8265492B2 (en) | 2006-03-31 | 2012-09-11 | Canon Kabushiki Kaisha | Image forming system and service person support method therefor |
JP2014237370A (ja) * | 2013-06-07 | 2014-12-18 | 三菱電機株式会社 | 列車情報管理システム |
US9164665B2 (en) | 2012-12-25 | 2015-10-20 | International Business Machines Corporation | Outputting management information based on state of managed object |
JP2015230522A (ja) * | 2014-06-03 | 2015-12-21 | Pfuテクニカルコミュニケーションズ株式会社 | 情報処理装置、診断順序決定方法及び制御プログラム |
JP2016110448A (ja) * | 2014-12-08 | 2016-06-20 | 株式会社デンソー | 診断・修理事例検索装置 |
WO2019012950A1 (ja) * | 2017-07-12 | 2019-01-17 | パナソニックIpマネジメント株式会社 | メンテナンス支援方法、及びメンテナンス支援用プログラム |
JP2019020811A (ja) * | 2017-07-12 | 2019-02-07 | パナソニックIpマネジメント株式会社 | メンテナンス支援方法、及びメンテナンス支援用プログラム |
WO2020165982A1 (ja) * | 2019-02-14 | 2020-08-20 | 三菱電機株式会社 | 故障支援装置、故障支援プログラム及び故障支援方法 |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7689873B1 (en) * | 2005-09-19 | 2010-03-30 | Google Inc. | Systems and methods for prioritizing error notification |
US7610512B2 (en) * | 2006-01-06 | 2009-10-27 | Hewlett-Packard Development Company, L.P. | System and method for automated and assisted resolution of it incidents |
JP4929001B2 (ja) * | 2007-03-19 | 2012-05-09 | 株式会社リコー | 表示処理システム、表示処理方法、および表示処理プログラム |
CN101567061B (zh) * | 2008-04-27 | 2012-05-23 | 梁杰 | 机械电子产品质量经济综合指标达到世界先进水平的方法 |
US20090300430A1 (en) * | 2008-06-02 | 2009-12-03 | Orit Nissan-Messing | History-based prioritizing of suspected components |
CN102012697A (zh) * | 2010-09-21 | 2011-04-13 | 三一重工股份有限公司 | 工程机械的智能故障处理方法与系统以及工程机械 |
JP5792508B2 (ja) * | 2011-05-02 | 2015-10-14 | シスメックス株式会社 | 検体処理装置 |
US8850274B2 (en) * | 2012-02-01 | 2014-09-30 | Empirix, Inc. | Method of embedding configuration data in a non-configuration document |
CN104680329A (zh) * | 2015-03-17 | 2015-06-03 | 中国农业银行股份有限公司 | 一种运维问题发生原因确定方法及装置 |
US10275300B2 (en) * | 2015-10-27 | 2019-04-30 | Oracle International Corporation | Systems and methods for prioritizing a support bundle |
CN106469098A (zh) * | 2016-09-19 | 2017-03-01 | 广州日滨科技发展有限公司 | 一种设备的故障处理方法和装置 |
JP6388683B1 (ja) * | 2017-04-10 | 2018-09-12 | 三菱電機ビルテクノサービス株式会社 | 監視システム及び監視システムにおける情報端末装置 |
JP6837017B2 (ja) * | 2018-01-17 | 2021-03-03 | 日本電信電話株式会社 | 作業手順提示装置及び作業手順提示方法、並びに、自動制御装置及び自動制御方法 |
JP7491674B2 (ja) | 2019-09-10 | 2024-05-28 | 東芝テック株式会社 | 保守支援装置、保守支援方法及びコンピュータプログラム |
JP7333281B2 (ja) * | 2020-02-06 | 2023-08-24 | 株式会社日立製作所 | 設計支援システム |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10124477A (ja) * | 1996-10-22 | 1998-05-15 | Hitachi Ltd | 故障診断方法 |
JP2001282944A (ja) * | 2000-03-31 | 2001-10-12 | Fujitsu General Ltd | インターネット利用のサービス支援システム |
JP2002024322A (ja) * | 2000-07-04 | 2002-01-25 | Inax Corp | 住宅機材の品番確定システム及び故障診断システム |
JP2002154085A (ja) * | 2000-11-15 | 2002-05-28 | Toyota Motor Corp | 作業用ロボットシステムの保全支援方法及び保全支援装置 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5127012A (en) * | 1991-02-19 | 1992-06-30 | Eastman Kodak Company | Diagnostic and administrative device for document production apparatus |
US5528516A (en) * | 1994-05-25 | 1996-06-18 | System Management Arts, Inc. | Apparatus and method for event correlation and problem reporting |
US5845272A (en) * | 1996-11-29 | 1998-12-01 | General Electric Company | System and method for isolating failures in a locomotive |
US6260048B1 (en) * | 1998-10-27 | 2001-07-10 | Hewlett-Packard Company | Resolution of incidents which occur during the use of a product |
EP1965326A3 (en) * | 1999-11-30 | 2008-12-31 | Sysmex Corporation | Support method, quality control method, and device therefor |
JP3612472B2 (ja) * | 2000-06-22 | 2005-01-19 | 株式会社日立製作所 | 遠隔監視診断システム、及び遠隔監視診断方法 |
WO2002007495A1 (de) * | 2000-07-22 | 2002-01-31 | Abb Research Ltd. | System zur unterstützung einer fehlerursachenanalyse |
US7027954B2 (en) * | 2001-12-21 | 2006-04-11 | Honeywell International Inc. | Method and apparatus for retrieving activity data related to an activity |
-
2003
- 2003-06-06 AU AU2003242223A patent/AU2003242223A1/en not_active Abandoned
- 2003-06-06 US US10/517,162 patent/US7050941B2/en not_active Expired - Fee Related
- 2003-06-06 EP EP03736059A patent/EP1533730A4/en not_active Withdrawn
- 2003-06-06 WO PCT/JP2003/007174 patent/WO2003105039A1/ja active Application Filing
- 2003-06-06 JP JP2004512040A patent/JPWO2003105039A1/ja active Pending
- 2003-06-06 CN CN038132451A patent/CN1659561A/zh active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10124477A (ja) * | 1996-10-22 | 1998-05-15 | Hitachi Ltd | 故障診断方法 |
JP2001282944A (ja) * | 2000-03-31 | 2001-10-12 | Fujitsu General Ltd | インターネット利用のサービス支援システム |
JP2002024322A (ja) * | 2000-07-04 | 2002-01-25 | Inax Corp | 住宅機材の品番確定システム及び故障診断システム |
JP2002154085A (ja) * | 2000-11-15 | 2002-05-28 | Toyota Motor Corp | 作業用ロボットシステムの保全支援方法及び保全支援装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP1533730A4 * |
Cited By (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006092183A (ja) * | 2004-09-22 | 2006-04-06 | Fuji Xerox Co Ltd | 画像形成装置の障害対処システムおよび方法 |
JP4506376B2 (ja) * | 2004-09-22 | 2010-07-21 | 富士ゼロックス株式会社 | 画像形成装置の障害対処システムおよび画像形成装置および管理装置および画像形成装置の障害対処システムの制御方法および管理装置の制御方法 |
US7555376B2 (en) | 2004-12-14 | 2009-06-30 | Snap-On Incorporated | Dynamic information method and system |
WO2006065328A1 (en) * | 2004-12-14 | 2006-06-22 | Snap-On Incorporated | Dynamic information method and system |
JP4717079B2 (ja) * | 2005-01-18 | 2011-07-06 | インターナショナル・ビジネス・マシーンズ・コーポレーション | コンピュータ・システムにおける障害の診断および保守のための方法およびシステム(疑わしいコンポーネントの履歴ベースの優先順位付け) |
JP2008527554A (ja) * | 2005-01-18 | 2008-07-24 | インターナショナル・ビジネス・マシーンズ・コーポレーション | コンピュータ・システムにおける障害の診断および保守のための方法およびシステム(疑わしいコンポーネントの履歴ベースの優先順位付け) |
WO2006077193A1 (en) * | 2005-01-18 | 2006-07-27 | International Business Machines Corporation | History-based prioritizing of suspected components |
US7409595B2 (en) | 2005-01-18 | 2008-08-05 | International Business Machines Corporation | History-based prioritizing of suspected components |
JP2007179535A (ja) * | 2005-11-29 | 2007-07-12 | Omron Corp | 不良対策選択装置、不良対策選択方法、不良対策選択用プログラム、および不良対策選択用プログラムを記録した記録媒体 |
US8265492B2 (en) | 2006-03-31 | 2012-09-11 | Canon Kabushiki Kaisha | Image forming system and service person support method therefor |
WO2009150737A1 (ja) * | 2008-06-12 | 2009-12-17 | 富士通株式会社 | 保守業務支援プログラム、保守業務支援方法および保守業務支援装置 |
GB2472736A (en) * | 2008-06-12 | 2011-02-16 | Fujitsu Ltd | Maintenance operation support program, maintenance operation support method and maintenance operation support device |
JP5012999B2 (ja) * | 2008-06-12 | 2012-08-29 | 富士通株式会社 | 保守業務支援プログラム、保守業務支援方法および保守業務支援装置 |
US9164665B2 (en) | 2012-12-25 | 2015-10-20 | International Business Machines Corporation | Outputting management information based on state of managed object |
JP2014237370A (ja) * | 2013-06-07 | 2014-12-18 | 三菱電機株式会社 | 列車情報管理システム |
JP2015230522A (ja) * | 2014-06-03 | 2015-12-21 | Pfuテクニカルコミュニケーションズ株式会社 | 情報処理装置、診断順序決定方法及び制御プログラム |
JP2016110448A (ja) * | 2014-12-08 | 2016-06-20 | 株式会社デンソー | 診断・修理事例検索装置 |
WO2019012950A1 (ja) * | 2017-07-12 | 2019-01-17 | パナソニックIpマネジメント株式会社 | メンテナンス支援方法、及びメンテナンス支援用プログラム |
JP2019020811A (ja) * | 2017-07-12 | 2019-02-07 | パナソニックIpマネジメント株式会社 | メンテナンス支援方法、及びメンテナンス支援用プログラム |
JP7113321B2 (ja) | 2017-07-12 | 2022-08-05 | パナソニックIpマネジメント株式会社 | 表示方法、表示プログラム、及び端末装置 |
WO2020165982A1 (ja) * | 2019-02-14 | 2020-08-20 | 三菱電機株式会社 | 故障支援装置、故障支援プログラム及び故障支援方法 |
JPWO2020165982A1 (ja) * | 2019-02-14 | 2021-03-25 | 三菱電機株式会社 | 故障支援装置、故障支援プログラム及び故障支援方法 |
Also Published As
Publication number | Publication date |
---|---|
CN1659561A (zh) | 2005-08-24 |
JPWO2003105039A1 (ja) | 2005-10-13 |
EP1533730A4 (en) | 2009-03-04 |
US20050177341A1 (en) | 2005-08-11 |
US7050941B2 (en) | 2006-05-23 |
EP1533730A1 (en) | 2005-05-25 |
AU2003242223A1 (en) | 2003-12-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2003105039A1 (ja) | トラブル対処支援システムおよびこれに接続される端末装置 | |
US8698616B2 (en) | Monitor control system | |
JP2001236115A (ja) | リモート診断システム及び方法 | |
US20090055720A1 (en) | Apparatus, and associated method, for generating an information technology incident report | |
CN111498634A (zh) | 电梯远程维护支持系统 | |
US20020103620A1 (en) | Apparatus management method, apparatus management system, and apparatus management program product | |
JP6837017B2 (ja) | 作業手順提示装置及び作業手順提示方法、並びに、自動制御装置及び自動制御方法 | |
JP2006085538A (ja) | 復旧支援方法及び復旧支援システム並びに復旧支援用プログラム | |
JP3291642B2 (ja) | 障害対策支援方法 | |
JP2592982B2 (ja) | 現場巡視支援装置 | |
JP3867868B2 (ja) | 障害統合管理装置 | |
JP2005259078A (ja) | 支援装置および管理システム | |
JPH1091475A (ja) | 障害復旧装置、障害復旧方法および障害復旧用プログラ ムを記憶した記憶媒体 | |
JPH09282351A (ja) | Cadシステム | |
JP3864286B2 (ja) | 空気調和機のサービスシステム及びサービス方法 | |
JPH11188584A (ja) | 稼動管理装置および稼動管理方法、記憶媒体 | |
JPH10111712A (ja) | 警報監視装置 | |
JP2000090162A (ja) | 作業指示・支援装置 | |
JPH1069400A (ja) | 計算機システムおよびその障害回復支援方法 | |
WO2023153287A1 (ja) | 試験条件決定装置 | |
JP2001147945A (ja) | 店舗業務進捗監視装置 | |
JP2014078151A (ja) | 電子日誌システム | |
JP2001117634A (ja) | 設備の巡回点検システム | |
JP6861653B2 (ja) | 監視制御支援装置 | |
JP2003150730A (ja) | メンテナンス管理システム、メンテナンス管理方法、及びメンテナンス対象ユーザマニュアル |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2004512040 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20038132451 Country of ref document: CN Ref document number: 10517162 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2003736059 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2003736059 Country of ref document: EP |