Method and system for providing problem identification and trouble-shooting services

• US 7,275,016 B2
• Filed: 08/08/2003
• Issued: 09/25/2007
• Est. Priority Date: 08/08/2003
• Status: Active Grant

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: Gross, Wolfgang, Hofler, Werner
• Primary Examiner(s): West; Jeffrey R.
• Application Number:
  US10/637,893
• Publication Number:
  US 20050033491A1
• Time in Patent Office: 1,509 Days
• Field of Search: 702/33, 702/35, 702/81, 702/84, 702/182, 702/183, 702/188, 702/185, 700/108, 700/110, 700/121, 705/1, 705/7, 705/11
• US Class Current: 702/182
• CPC Class Codes: G05B 19/4184 characterised by fault tolerance, reliability of production system
• CPC Class Codes: G05B 2219/31324 Distributed real time knowledge, database
• CPC Class Codes: G05B 2219/32235 Sharing of data between process control and maintenance management computers
• CPC Class Codes: Y02P 90/02 Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Abstract

In a complex plant most of the problems or errors will occur only once. Therefore corrective maintenance and trouble-shooting staff can not go back or hark back to ready-made solutions for these problems or errors. The present invention provides a method and a computerized system which enables the corrective maintenance and trouble-shooting staff having access to experiences made on third party plants regarding these problems or errors.

Claims

1. A method for providing problem identification or trouble-shooting services in production plants, said method comprising the steps of:

providing a forum on a networking server for collecting solutions for problems that occur at a plurality of plants, at least some of which plants are remote from each other;

obtaining sets of problem/solution data resulting from respective problems and solutions in at least one of the plants, at least some of the sets of problem/solution data comprising identification of a component involved in a respective problem, a parameter of the component, an environmental parameter, and a solution to the respective problem;

storing respective representations of the sets of problem/solution data on a database of the networking server;

obtaining a subsequent set of problem data resulting from a subsequent problem in an inquiring one of the plants, the subsequent set of problem data comprising identification of a component involved in the problem, a parameter of the component, and an environmental parameter;

creating a search pattern from the subsequent set of problem data;

searching the database for at least one of the stored representations of the sets of plant problem/solution data that at least approximately matches criteria in the search pattern;

transferring a solution found in the searching step to the inquiring plant;

applying the solution found in the searching step to the subsequent problem in the inquiring plant;

returning feedback from the inquiring plant to the networking server, the feedback comprising an indication of relevance of the solution found and an indication of the success of the solution found;

determining, from the feedback, criteria in the search pattern with the highest relevance in finding a solution to the subsequent problem;

optimizing an inquiry mechanism and a comparison mechanism in the networking server based on results of the determining step to improve subsequent performances of the searching step to improve diagnosis and maintenance functions in the inquiring plant; and

automatically polling the plurality of plants to update the problem/solution data.

2. The method according to claim 1, wherein at least some of the sets of problem/solution data comprise a plant type identifier, a type of plant predecessor and/or successor, a content of a diagnosis buffer, and at least one error message.

3. The method according to claim 2, wherein at least some of the sets of problem/solution data comprise a component type identifier, a type of component predecessor and/or successor, a content of a diagnosis buffer, and at least one error message.