Supplier teardown & analysis reporting system

• US 20070294052A1
• Filed: 06/16/2006
• Published: 12/20/2007
• Est. Priority Date: 06/16/2006
• Status: Abandoned Application

• Current Assignee: Sikorsky Aircraft Corporation (Martin Marietta Corporation)
• Original Assignee: Sikorsky Aircraft Corporation (Martin Marietta Corporation)
• Inventors: Stathis, George L., Tran, Cu V.
• Application Number:
  US11/454,466
• Publication Number:
  US 20070294052A1
• Time in Patent Office: Days
• US Class Current: 702/185
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A Supplier Teardown and Analysis Reporting System (STARS) captures information pertaining to component removals or failures that caused an unscheduled maintenance action. The detailed data facilitates design engineers understanding of failure drivers and propose improvements and commence implementation of a Corrective Action Plan at the earliest practicable time.

Claims

1. A method of tracking repaired components comprising the steps of:

(A) inputting data pertaining to unscheduled maintenance of a repaired component by a repair facility user;

(B) communicating data from said step (A) to an OEM; and

(C) compiling the data from said step (B) to facilitate failure analysis tracking of a multiple of the repaired components.

2. A method as recited in claim 1, further comprises the step of:

(D) determination a root cause from said step (C).

3. A method as recited in claim 2, further comprises the step of:

(E) determination a proposed corrective action from said step (D).

4. A method as recited in claim 1, wherein said step (A) further comprises the steps of:

(a) inputting a failure analysis description of the repaired component.

5. A method as recited in claim 1, wherein said step (A) further comprises the steps of:

(a) inputting a root cause of a failure of the repaired component.

6. A method as recited in claim 5, wherein said step (A) further comprises the steps of:

(b) inputting substantiating data for the root cause.

7. A method as recited in claim 6, wherein said step (A) further comprises the steps of:

(c) inputting a proposed corrective action.

8. A method as recited in claim 7, wherein said step (c) further comprises the step of:

(i) inputting substantiating data for the proposed corrective action to demonstrate that the proposed corrective action is cost effective.

9. A method as recited in claim 1, further comprises the step of:

(D) inputting data regarding related components that may contribute to the unscheduled maintenance.

15. A method as recited in claim 1, further comprising the step of:

(E) determination a Corrective Action Plan in response to said step (D).

10. A method of tracking repaired components comprising the steps of:

(A) inputting data pertaining to a failure analysis from an unscheduled maintenance of a repaired component by a repair facility user;

(B) inputting data pertaining to a root cause of the unscheduled maintenance of the repaired component by the repair facility user;

(C) inputting data pertaining to a proposed corrective action for the root cause of said step (B) by the repair facility user;

(D) communicating data from said steps (A-C) to an OEM; and

(E) compiling the data at the OEM to facilitate failure analysis tracking of a multitude of the repaired components.

11. A method as recited in claim 10, wherein said step (A) further comprises the steps of:

(a) inputting substantiating data for the failure analysis.

12. A method as recited in claim 10, wherein said step (B) further comprises the steps of:

(a) inputting substantiating data for the root cause.

13. A method as recited in claim 10, wherein said step (C) further comprises the steps of:

(a) inputting substantiating data for the proposed corrective action to demonstrate that the proposed corrective action is cost effective.

14. A method of tracking repaired components comprising the steps of:

(A) receiving data pertaining to a failure analysis from an unscheduled maintenance of a repaired component;

(B) receiving data pertaining to a root cause of the unscheduled maintenance of the repaired component;

(C) receiving data pertaining to a proposed corrective action for the root cause of said step (B); and

(D) compiling the data from said steps (A-C) to facilitate failure analysis tracking of a multitude of the repaired components.