WO2007149296A2 - Supplier teardown and analysis reporting system - Google Patents

Supplier teardown and analysis reporting system Download PDF

Info

Publication number
WO2007149296A2
WO2007149296A2 PCT/US2007/013958 US2007013958W WO2007149296A2 WO 2007149296 A2 WO2007149296 A2 WO 2007149296A2 US 2007013958 W US2007013958 W US 2007013958W WO 2007149296 A2 WO2007149296 A2 WO 2007149296A2
Authority
WO
WIPO (PCT)
Prior art keywords
data
inputting
recited
steps
corrective action
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2007/013958
Other languages
French (fr)
Other versions
WO2007149296A3 (en
Inventor
George L. Stathis
Cu V. Tran
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sikorsky Aircraft Corp
Original Assignee
Sikorsky Aircraft Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sikorsky Aircraft Corp filed Critical Sikorsky Aircraft Corp
Priority to EP07809551A priority Critical patent/EP2028928A4/en
Priority to BRPI0713459-2A priority patent/BRPI0713459A2/en
Publication of WO2007149296A2 publication Critical patent/WO2007149296A2/en
Publication of WO2007149296A3 publication Critical patent/WO2007149296A3/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Definitions

  • the present invention relates to an integrated system and method for tracking component repairs, and more particularly to a system and method used to document the reported discrepancy, failure analysis, root cause and proposed corrective action(s) for nonconforming components.
  • the integrated tracking system provides a Supplier Teardown and Analysis Reporting System (STARS) which captures information pertaining to component removals or failures that caused an unscheduled maintenance action.
  • STS Supplier Teardown and Analysis Reporting System
  • the detailed data facilitates design engineer understanding of the failure drivers to propose improvements and commence implementation of a Corrective Action Plan at the earliest practicable time.
  • the present invention therefore provides an integrated system and a method for tracking component repairs which facilitates failure analysis for determination of root cause and proposed corrective action(s).
  • Figure 1 is a schematic block diagram of a supplier teardown and analysis reporting system
  • Figure 2 is a screen shot from the supplier teardown and analysis reporting system utilizing a spindle assembly as an example component repair;
  • Figure 3A is a perspective view of the spindle assembly described in the screen shot illustrated in Figure 2;
  • Figure 3B is an exploded view of a root cause description of the example spindle assembly.
  • Figure 4 is an example of a supplier teardown and analysis report generated from the supplier teardown and analysis reporting system as would be generated from the information input at Figure 2.
  • FIG. 1 illustrates an integrated tracking system 20 for tracking repaired components or systems in a block diagram format.
  • the system 20 interconnects any number of repair facility FTP sites 22a-22n with an aircraft OEM file server 24 through a communication system 26 such as the Internet, email, or any suitable transfer or downloading technique known in the art.
  • Each repair facility is typically a remote location such as various repair facility sites, supplier sites, and company business unit sites.
  • repair facility as utilized herein may include any facility which receives components or systems from the OEM or the fleet. That is, a typical "black box" component or system is typically removed from the aircraft and returned to the OEM or designated repair facility. Once repaired, the component or system was heretofore returned to the original operator for immediate use or entry into maintenance stores for later use.
  • the aircraft OEM filer server 24 includes a centralized component repair information database 28.
  • the centralized component repair information database 28 is referred to herein as a Supplier Teardown and Analysis Reporting System (STARS).
  • STS Supplier Teardown and Analysis Reporting System
  • Information about repaired components or systems is entered at the repair facility FTP sites 22a-22n.
  • Data within the repair facility FTP sites 22a-22n about the repaired components or systems is communicated from each of the aforementioned locations to the aircraft OEM 24.
  • various server systems will also be usable with the present invention and that the illustrated embodiment of server systems are for descriptive purposed only.
  • the data typically includes information pertaining to component removals or failures that caused an unscheduled maintenance as well as other information as disclosed in the screen shot ( Figure 2)of the illustrated embodiment which utilizes a spindle assembly ( Figures 3A and 3B) as an example component which has been sent out to a repair facility.
  • the database 28 may be programmed in any suitable computer language such as Microsoft Access or the like generally known in the art to carry out the herein described functionality.
  • the data entry screen allows the repair facility to enter or update data in the system and to navigate through database records via the action command buttons located on the right of the screen.
  • Most of the data fields are self- explanatory. The description and data type for each field are provided in the Appendix. Some data fields have a drop-down feature for quicker and easier data entry. Drop-down lists also help to ensure that the data that is entered in a field is consistent.
  • the data entry screen is preferably divided into the following sections: [0019] UPPER SECTION (FAILED COMPONENT INFORMATION) [0020] This section of the screen contains general information about the specific failed component that is returned to supplier for teardown and/or failure evaluation. It is preferably a mandatory requirement to create a new record for each returned component. When a new record is added to the system to document activities performed on a particular failed component, a record number will be assigned to the TAR Number data field. Data type for the TAR Number is an AutoNumber field that automatically enters a number when a record is added. Preferably, once a record number is generated, it can't be deleted or changed.
  • the repair facility is encouraged to record information from paper documentations that are returned along with the failed component.
  • Field information such as: TSN (Time Since New), TSR (Time Since Repair), and Removal Malfunction etc. can be very useful during the component investigation.
  • the primary purpose of the STARS 20 is to capture information pertaining to component removals or failures that caused an unscheduled maintenance action. Therefore, detailed data information provided in this section facilitates design engineer understanding of the failure drivers to propose improvements and commence implementation of a Corrective Action Plan at the earliest practicable time. Definitions for some of data fields in this section are as follow:
  • a Failure Trent shall be defined as the establishment of two or more occurrences of the identical unscheduled maintenance event/failure symptom.
  • Root Cause Identify the root cause of the failure with substantiating data such as photos, drawings, op-sheets, test and met - lab reports, inspection results and measurements, and analyses which identify the root cause and link it to the Reported Discrepancy.
  • - Proposed Corrective Action Identify the corrective action that specifically addresses the identified root cause. Substantiate that the corrective action is cost effective in addressing the cause. (E.g. A special inspection may address symptoms and identify that a problem has occurred, but may not be cost effectively in preventing the root cause from reoccurring).
  • This section contains detail piece components or sub-assemblies that may contribute to the reported failure.
  • an electronic system that has several Circuit Card Assemblies (CCAs) may be removed from an aircraft due to a reported "Internal Failure.”
  • CCAs Circuit Card Assemblies
  • the repair facility should enter information about individual CCAs in this section.
  • the repair facility shall perform a failure analysis on all: (i) in-house or reported failures; and (ii) reported unscheduled maintenance actions when either a failure trend is established (“Failure Trend") or flight safety is involved (collectively or individual "Failure”)-
  • a Failure Trend shall be defined as the establishment of two or more occurrences of the identical unscheduled maintenance event / failure symptom.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Operations Research (AREA)
  • Physics & Mathematics (AREA)
  • Educational Administration (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Game Theory and Decision Science (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • General Factory Administration (AREA)
  • Exhaust Gas After Treatment (AREA)
  • Maintenance And Inspection Apparatuses For Elevators (AREA)

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.

Description

SUPPLIER TEARDOWN & ANALYSIS REPORTING SYSTEM
BACKGROUND OF THE INVENTION
[0001] This invention was made with government support under Contract No.:N00383-04-D-028N with the United States Navy. The government therefore has certain rights in this invention.
[0002] The present invention relates to an integrated system and method for tracking component repairs, and more particularly to a system and method used to document the reported discrepancy, failure analysis, root cause and proposed corrective action(s) for nonconforming components.
[0003] Currently, information pertaining to a component or system removal or failure that caused an unscheduled maintenance event may or may not be retained by the repair facility. However, even if retained at the repair facility, the information is not transmitted back to the OEM or customer who first sent the component or system out for repair. That is, the OEM or customer who sent out the defective component or system will receive a repaired or replacement component or system without a detailed description of the failure or repair that was performed at the repair facility.
[0004] Although effective, the lack of a detailed description of the failure or repair that was performed at the repair facility prevents an OEM or customer from centralizing the reliability performance database, trending the information to identify potential fleet impact or from utilizing the data as a basis to explore potential continued improvements.
[0005] Accordingly, it is desirable to provide an integrated system and a method for tracking component repairs which facilitates failure analysis for determination of root cause and proposed corrective action(s).
SUMMARY OF THE INVENTION
[0006] The integrated tracking system according to the present invention provides a Supplier Teardown and Analysis Reporting System (STARS) which captures information pertaining to component removals or failures that caused an unscheduled maintenance action. The detailed data facilitates design engineer understanding of the failure drivers to propose improvements and commence implementation of a Corrective Action Plan at the earliest practicable time.
[0007] The present invention therefore provides an integrated system and a method for tracking component repairs which facilitates failure analysis for determination of root cause and proposed corrective action(s).
BRIEF DESCRIPTION OF THE DRAWINGS
[0008] The various features and advantages of this invention will become apparent to those skilled in the art from the following detailed description of the currently preferred embodiment. The drawings that accompany the detailed description can be briefly described as follows:
[0009] Figure 1 is a schematic block diagram of a supplier teardown and analysis reporting system;
[0010] Figure 2 is a screen shot from the supplier teardown and analysis reporting system utilizing a spindle assembly as an example component repair;
[0011] Figure 3A is a perspective view of the spindle assembly described in the screen shot illustrated in Figure 2;
[0012] Figure 3B is an exploded view of a root cause description of the example spindle assembly; and
[0013] Figure 4 is an example of a supplier teardown and analysis report generated from the supplier teardown and analysis reporting system as would be generated from the information input at Figure 2.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
[0014] Figure 1 illustrates an integrated tracking system 20 for tracking repaired components or systems in a block diagram format. The system 20 interconnects any number of repair facility FTP sites 22a-22n with an aircraft OEM file server 24 through a communication system 26 such as the Internet, email, or any suitable transfer or downloading technique known in the art. Each repair facility is typically a remote location such as various repair facility sites, supplier sites, and company business unit sites. It should be understood that repair facility as utilized herein may include any facility which receives components or systems from the OEM or the fleet. That is, a typical "black box" component or system is typically removed from the aircraft and returned to the OEM or designated repair facility. Once repaired, the component or system was heretofore returned to the original operator for immediate use or entry into maintenance stores for later use.
[0015] The aircraft OEM filer server 24 includes a centralized component repair information database 28. The centralized component repair information database 28 is referred to herein as a Supplier Teardown and Analysis Reporting System (STARS).
[0016] Information about repaired components or systems is entered at the repair facility FTP sites 22a-22n. Data within the repair facility FTP sites 22a-22n about the repaired components or systems is communicated from each of the aforementioned locations to the aircraft OEM 24. It should be understood that various server systems will also be usable with the present invention and that the illustrated embodiment of server systems are for descriptive purposed only. The data typically includes information pertaining to component removals or failures that caused an unscheduled maintenance as well as other information as disclosed in the screen shot (Figure 2)of the illustrated embodiment which utilizes a spindle assembly (Figures 3A and 3B) as an example component which has been sent out to a repair facility. The database 28 may be programmed in any suitable computer language such as Microsoft Access or the like generally known in the art to carry out the herein described functionality.
[0017] Referring to Figure 2, the data entry screen allows the repair facility to enter or update data in the system and to navigate through database records via the action command buttons located on the right of the screen. Most of the data fields are self- explanatory. The description and data type for each field are provided in the Appendix. Some data fields have a drop-down feature for quicker and easier data entry. Drop-down lists also help to ensure that the data that is entered in a field is consistent.
[0018] The data entry screen is preferably divided into the following sections: [0019] UPPER SECTION (FAILED COMPONENT INFORMATION) [0020] This section of the screen contains general information about the specific failed component that is returned to supplier for teardown and/or failure evaluation. It is preferably a mandatory requirement to create a new record for each returned component. When a new record is added to the system to document activities performed on a particular failed component, a record number will be assigned to the TAR Number data field. Data type for the TAR Number is an AutoNumber field that automatically enters a number when a record is added. Preferably, once a record number is generated, it can't be deleted or changed.
[0021] The repair facility is encouraged to record information from paper documentations that are returned along with the failed component. Field information such as: TSN (Time Since New), TSR (Time Since Repair), and Removal Malfunction etc. can be very useful during the component investigation.
[0022] MIDDLE SECTION (ROOT CAUSE ANALYSIS AND CORRECTIVE ACTION)
[0023] The primary purpose of the STARS 20 is to capture information pertaining to component removals or failures that caused an unscheduled maintenance action. Therefore, detailed data information provided in this section facilitates design engineer understanding of the failure drivers to propose improvements and commence implementation of a Corrective Action Plan at the earliest practicable time. Definitions for some of data fields in this section are as follow:
[0024] - Failure Analysis Description: Description of how the root cause of the reported problem was determined. The repair facility shall perform a failure analysis on all: (i) in-house or reported failures; and (ii) reported unscheduled maintenance actions when either a failure trend is established ("Failure Trend") or flight safety is involved (collectively or individual "Failure"). A Failure Trent shall be defined as the establishment of two or more occurrences of the identical unscheduled maintenance event/failure symptom.
[0025] - Root Cause: Identify the root cause of the failure with substantiating data such as photos, drawings, op-sheets, test and met - lab reports, inspection results and measurements, and analyses which identify the root cause and link it to the Reported Discrepancy.
[0026] - Proposed Corrective Action: Identify the corrective action that specifically addresses the identified root cause. Substantiate that the corrective action is cost effective in addressing the cause. (E.g. A special inspection may address symptoms and identify that a problem has occurred, but may not be cost effectively in preventing the root cause from reoccurring).
[0027] LEFT BOTTOM SECTION (SUPPORTING DOCUMENTS/PICTURES)
[0028] This section of the screen permits photos, documents, presentations and the like that support the failure analysis, root cause and corrective action entries. [0029] RIGHT BOTTOM SECTION (DISPOSITION OF FAILED COMPONENTS)
[0030] This section contains detail piece components or sub-assemblies that may contribute to the reported failure. For example only, an electronic system that has several Circuit Card Assemblies (CCAs) may be removed from an aircraft due to a reported "Internal Failure." During the subsequent teardown/testing process at the repair facility, some CCAs were found inoperable due to corrosion, fatigue, shorts, etc. The repair facility should enter information about individual CCAs in this section.
[0031] Once data is input into STARS, suppliers may email the MS Access data Table File ("SupplierTAR_be.mdb") and any supporting information contained in the STARS application folder ("DocumentsPictures") to an email address of the OEM. The inputted data may also be printed as a report (Figure 4) for attachment with the returned repaired components and systems or for other recordation usage.
[0032] APPENDIX
Figure imgf000007_0001
Figure imgf000008_0001
Figure imgf000009_0001
Figure imgf000010_0001
[0033] The repair facility shall perform a failure analysis on all: (i) in-house or reported failures; and (ii) reported unscheduled maintenance actions when either a failure trend is established ("Failure Trend") or flight safety is involved (collectively or individual "Failure")- A Failure Trend shall be defined as the establishment of two or more occurrences of the identical unscheduled maintenance event / failure symptom.
[0034] Although particular step sequences are shown, described, and claimed, it should be understood that steps may be performed in any order, separated or combined unless otherwise indicated and will still benefit from the present invention.
[0035] The foregoing description is exemplary rather than defined by the limitations within. Many modifications and variations of the present invention are possible in light of the above teachings. The preferred embodiments of this invention have been disclosed, however, one of ordinary skill in the art would recognize that certain modifications would come within the scope of this invention. It is, therefore, to be understood that within the scope of the appended claims, the invention may be practiced otherwise than as specifically described. For that reason the following claims should be studied to determine the true scope and content of this invention.

Claims

CLAIMSWhat is claimed is:
1. A method of tracking repaired components icomprising 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.
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.
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).
PCT/US2007/013958 2006-06-16 2007-06-13 Supplier teardown and analysis reporting system Ceased WO2007149296A2 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP07809551A EP2028928A4 (en) 2006-06-16 2007-06-13 Supplier teardown and analysis reporting system
BRPI0713459-2A BRPI0713459A2 (en) 2006-06-16 2007-06-13 method of tracking repaired components

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/454,466 US20070294052A1 (en) 2006-06-16 2006-06-16 Supplier teardown & analysis reporting system
US11/454,466 2006-06-16

Publications (2)

Publication Number Publication Date
WO2007149296A2 true WO2007149296A2 (en) 2007-12-27
WO2007149296A3 WO2007149296A3 (en) 2008-12-04

Family

ID=38833990

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2007/013958 Ceased WO2007149296A2 (en) 2006-06-16 2007-06-13 Supplier teardown and analysis reporting system

Country Status (5)

Country Link
US (1) US20070294052A1 (en)
EP (1) EP2028928A4 (en)
CN (1) CN101472468A (en)
BR (1) BRPI0713459A2 (en)
WO (1) WO2007149296A2 (en)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9904928B1 (en) 2014-07-11 2018-02-27 State Farm Mutual Automobile Insurance Company Method and system for comparing automatically determined crash information to historical collision data to detect fraud
US10474973B2 (en) * 2015-05-19 2019-11-12 Bell Helicopter Textron Inc. Aircraft fleet maintenance system
US11049333B2 (en) 2017-09-14 2021-06-29 Textron Innovations Inc. On-component tracking of maintenance, usage, and remaining useful life
FR3075435A1 (en) * 2017-12-20 2019-06-21 Dassault Aviation METHOD FOR IMPLEMENTING ACTIONS IN THE DESIGN, MANUFACTURE AND OPERATION OF AN AIRCRAFT FLEET AND ASSOCIATED SYSTEM
US10974851B2 (en) 2018-11-09 2021-04-13 Textron Innovations Inc. System and method for maintaining and configuring rotorcraft
CN111324070B (en) * 2020-03-04 2021-07-13 明峰医疗系统股份有限公司 Debugging method of CT serial detector module cluster based on FPGA

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5210704A (en) * 1990-10-02 1993-05-11 Technology International Incorporated System for prognosis and diagnostics of failure and wearout monitoring and for prediction of life expectancy of helicopter gearboxes and other rotating equipment
US5687315A (en) * 1992-04-16 1997-11-11 Hitachi, Ltd. Support system for constructing an integrated network
US6112015A (en) * 1996-12-06 2000-08-29 Northern Telecom Limited Network management graphical user interface
US6154728A (en) * 1998-04-27 2000-11-28 Lucent Technologies Inc. Apparatus, method and system for distributed and automatic inventory, status and database creation and control for remote communication sites
US6263322B1 (en) * 1998-07-07 2001-07-17 Hunter Engineering Company Integrated automotive service system and method
US6134557A (en) * 1998-11-20 2000-10-17 Matlink, Inc. Materials and supplies ordering system
US6345257B1 (en) * 1998-12-14 2002-02-05 National Railroad Passenger Corporation Computer based interactive defect reporting system for the paperless reporting of problems in a vehicle forming part of a fleet
US6349268B1 (en) * 1999-03-30 2002-02-19 Nokia Telecommunications, Inc. Method and apparatus for providing a real time estimate of a life time for critical components in a communication system
US6535890B2 (en) * 1999-11-16 2003-03-18 Aircraft Technical Publishers Computer aided maintenance and repair information system for equipment subject to regulatory compliance
US6691006B2 (en) * 1999-12-01 2004-02-10 Sinex Aviation Technologies Corporation Dynamic assignment of maintenance tasks to aircraft maintenance personnel
US6684349B2 (en) * 2000-01-18 2004-01-27 Honeywell International Inc. Reliability assessment and prediction system and method for implementing the same
US7020620B1 (en) * 2000-06-23 2006-03-28 Basf Corporation Computer-implemented vehicle repair analysis system
US6738748B2 (en) * 2001-04-03 2004-05-18 Accenture Llp Performing predictive maintenance on equipment
US7440906B1 (en) * 2001-09-04 2008-10-21 Accenture Global Services Gmbh Identification, categorization, and integration of unplanned maintenance, repair and overhaul work on mechanical equipment
US7124059B2 (en) * 2000-10-17 2006-10-17 Accenture Global Services Gmbh Managing maintenance for an item of equipment
US7136832B2 (en) * 2000-12-07 2006-11-14 Savi Technology, Inc. Supply chain visibility for real-time tracking of goods
AU2001255568A1 (en) * 2000-12-29 2002-07-16 General Electric Company Method and system for identifying repeatedly malfunctioning equipment
US6574537B2 (en) * 2001-02-05 2003-06-03 The Boeing Company Diagnostic system and method
US6795799B2 (en) * 2001-03-07 2004-09-21 Qualtech Systems, Inc. Remote diagnosis server
US6567729B2 (en) * 2001-03-28 2003-05-20 Pt Holdings Ltd. System and method of analyzing aircraft removal data for preventative maintenance
US6885903B2 (en) * 2001-07-10 2005-04-26 General Electric Company Method and system for tracking repair of components
US6871160B2 (en) * 2001-09-08 2005-03-22 Scientific Monitoring Inc. Intelligent condition-based engine/equipment management system
US6785582B2 (en) * 2002-02-25 2004-08-31 United Technologies Corporation Integrated tracking system
US6892159B2 (en) * 2002-05-17 2005-05-10 Sun Microsystems, Inc. Method and system for storing field replaceable unit operational history information
US7047159B2 (en) * 2002-07-31 2006-05-16 Sap Aktiengesellschaft Component tagging with maintenance related information including maintenance procedures

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of EP2028928A4 *

Also Published As

Publication number Publication date
EP2028928A4 (en) 2011-08-03
CN101472468A (en) 2009-07-01
WO2007149296A3 (en) 2008-12-04
EP2028928A2 (en) 2009-03-04
US20070294052A1 (en) 2007-12-20
BRPI0713459A2 (en) 2012-02-22

Similar Documents

Publication Publication Date Title
US6003808A (en) Maintenance and warranty control system for aircraft
US20220058750A1 (en) Communication of insurance claim data
US8175732B2 (en) Manufacturing system and method
US7895470B2 (en) Collecting and representing knowledge
WO2007149296A2 (en) Supplier teardown and analysis reporting system
US20020123915A1 (en) Methods and systems for aviation nonconformance component management
CN110032169A (en) Breakdown maintenance bootstrap technique and device
CN101563694A (en) Manufactured product configuration
US20120209846A1 (en) Document processing system and computer readable medium
JP2022081952A (en) Distributed system and data transmission method
JP2006011744A (en) Defect recurrence prevention device, defect recurrence prevention method, program, and recording medium
KR101020132B1 (en) Automated Test System and Method of Financial Business Program
US6859676B1 (en) Method of improving quality of manufactured modules
US12548389B1 (en) System and method for documentation of vehicle repair services
Ho et al. Asset data quality—a case study on mobile mining assets
US20010053990A1 (en) Construction of system with reduced load on system engineers
Al-Mashari et al. Enterprise resource planning of business process systems
JP2007115038A (en) Printed circuit board quality information management system
KR100527299B1 (en) Network system for managing fault in air traffic
US20230025013A1 (en) Related Data Extraction Apparatus, Related Data Extraction System, Related Data Extraction Method, and Related Data Extraction Program
JP2004054689A (en) Newly employed parts check registration system and method
English IQ and Muda; Information Quality Eliminates Waste
CA2592525C (en) Warranty claim report generating system for aircraft
Okorie et al. More Than 10 Years on: Does a State‐of‐the‐Art Review and Synthesis Offer New Frameworks to Guide Future Design for Remanufacturing Research?
Baudin Maintenance information systems

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200780022431.6

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07809551

Country of ref document: EP

Kind code of ref document: A2

WWE Wipo information: entry into national phase

Ref document number: 2007809551

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

ENP Entry into the national phase

Ref document number: PI0713459

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20081216