Method, system and storage medium for managing automated system events

• US 20060085084A1
• Filed: 10/19/2004
• Published: 04/20/2006
• Est. Priority Date: 10/19/2004
• Status: Active Grant

• Current Assignee: GM Global Technology Operations LLC (General Motors Company)
• Original Assignee: GM Global Technology Operations Incorporated (Motors Liquidation Co. GUC Trust)
• Inventors: Baker, Henry W., Nickolaou, James N.
• Granted Patent: US 7,333,024 B2
• Time in Patent Office: Days
• US Class Current: 700/12
• CPC Class Codes: G05B 19/4184 characterised by fault tolerance, reliability of production system
• CPC Class Codes: G05B 2219/31356 Automatic fault detection and isolation
• CPC Class Codes: G05B 2219/31439 Alarms can be warning, alert or fault
• CPC Class Codes: G05B 2219/32209 Stop production line
• CPC Class Codes: G05B 23/0227 Qualitative history assessment, whereby the type of data acted upon, e.g. waveforms, images or patterns, is not relevant, e.g. rule based assessment; if-then decisions
• CPC Class Codes: G05B 23/0275 Fault isolation and identification, e.g. classify fault; estimate cause or root of failure
• CPC Class Codes: Y02P 90/02 Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Abstract

Disclosed herein is a method, system and storage medium for managing automated system events. The method includes identifying events that are a defined system event and associating the events identified with one of (a) events that cause an automated system to transition from an automatic cycle mode, the events having a fault type associated therewith; and (b) events that do not cause the automated system to transition from the automatic cycle mode. The method also includes generating a listing of the events identified with regard to the associating the events.

Claims

1. A method for managing automated system events, comprising:

identifying events that are a defined system event;

associating the events identified with one of (a) events that cause an automated system to transition from an automatic cycle mode, the events having a fault type associated therewith; and

(b) events that do not cause the automated system to transition from the automatic cycle mode; and

generating a listing of the events identified with regard to the associating the events.

2. The method of claim 1, wherein the identifying events that are a defined system event is performed in response to detecting a change in the automated system'"'"'s operating condition.

3. The method of claim 1, further comprising:

tracking a total duration of the system event.

4. The method of claim 3, wherein tracking a total duration of the system event includes separating the duration into response time and repair time.

5. The method of claim 1, further comprising:

organizing and storing the listing of the events identified into a searchable database.

6. The method of claim 1, further comprising:

custom-defining data to be collected from the automated system.

7. The method of claim of claim 6, wherein the custom-defining includes associating an algebraic expression or boolean condition with data points for collection.

8. The method of claim 1, wherein the system event includes at least one of a:

machine fault;

blocked state;

starved state;

an overcycle;

a reject part; and

an empty pallet.

9. The method of claim 1, wherein the fault type includes one of:

a level 1 fault;

a level 2 fault; and

a level 2.5 fault.

10. A system for managing automated system events, comprising:

an automated system;

a user system in communication with the automated system via a network, the user system including a processor;

a collector component in communication with the automated system;

a system event manager application executing in conjunction with the collector component; and

at least one timer in communication with at least one of the automated system and the system event manager application, the system event manager application performing;

identifying events that are a defined system event;

associating the events identified with one of (a) events that cause the automated system to transition from an automatic cycle mode, the events having a fault type associated therewith; and

(b) events that do not cause the automated system to transition from the automatic cycle mode; and

generating a listing of the events identified with regard to the associating the events.

11. The system of claim 10, wherein the identifying events that are a defined system event is performed in response to detecting a change in the automated system'"'"'s operating condition.

12. The system of claim 10, wherein the at least one timer tracks a total duration of the system event.

13. The system of claim 12, wherein the at least one timer separates the total duration into response time and repair time.

14. The system of claim 10, further comprising:

a data repository in communication with the collector component, the System event manager application, and the user system, the data repository including a searchable database storing the listing of events identified.

15. The system of claim 10, further comprising:

unique condition groupings of data points that are custom-defined for collection by the collector component.

16. The system of claim of claim 15, wherein the unique condition groupings of data points include an algebraic expression or boolean condition associated with two or more data points.

17. The system of claim 10, wherein the system event includes at least one of a:

machine fault;

blocked state;

starved state;

an overcycle;

a reject part; and

an empty pallet.

18. The system of claim 10, wherein the fault type includes one of:

a level 1 fault;

a level 2 fault; and

a level 2.5 fault.

19. A storage medium encoded with machine-readable program code for managing automated system events, the program code including instructions for causing a processor to implement a method, comprising:

identifying events that are a defined system event;

associating the events identified with one of (a) events that cause an automated system to transition from an automatic cycle mode, the events having a fault type associated therewith; and

(b) events that do not cause the automated system to transition from the automatic cycle mode; and

generating a listing of the events identified with regard to the associating the events.

20. The storage medium of claim 19, wherein the identifying events that are a defined system event is performed in response to detecting a change in the automated system'"'"'s operating condition.