CA2330216A1 - Methods and systems for aviation component repair services - Google Patents
Methods and systems for aviation component repair services Download PDFInfo
- Publication number
- CA2330216A1 CA2330216A1 CA002330216A CA2330216A CA2330216A1 CA 2330216 A1 CA2330216 A1 CA 2330216A1 CA 002330216 A CA002330216 A CA 002330216A CA 2330216 A CA2330216 A CA 2330216A CA 2330216 A1 CA2330216 A1 CA 2330216A1
- Authority
- CA
- Canada
- Prior art keywords
- repair
- information
- status
- quote
- inspection
- 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.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
Abstract
A system for accessing aircraft engine component repair information by internal users and external customers is described. The system includes a server, at least one computer and a network connecting the computers to the server. The server is configured with a database of repair order and quote information and a plurality of user interfaces associated with the repair information. The user interfaces allows a user to input information into the database, which is downloaded to the customer in response to an inquiry.
Description
METHODS AND SYSTEMS FOR AVIATION
COMPONENT REPAIR SERVICES
CROSS REFERENCE TO RELATED APPLICATIONS
This application claims the benefit of U.S. Provisional Application No.
60/175,178, filed January 7, 2000, which is hereby incorporated by reference in its entirety.
BACKGROUND OF THE INVENTION
This invention relates generally to customer services, and more specifically to methods and systems for accessing turbine engine aircraft components repair order information and services.
Manufacturers of aircraft engines normally provide repair and inspection services for engine and engine components. However, after an inspection of the engine has been completed, or engine component parts sent in for repair have been repaired, communicating the inspection results to engine owners, e.g.
customers, has typically been a time consuming and potentially frustrating process for both the engine manufacturer and the customer. Currently communicating inspection results from incoming inspections of aircraft engines or component parts typically involves reporting the results in tabular form, and submitting the reports to customers via mail or facsimile. In addition, variations in the inspections of different facilities is a source of customer concern.
It would be desirable to provide incoming inspection reports to customers which include information in addition to known tabular reports.
Since, customers often desire photographs of damaged components or parts found during the incoming inspections, it would be further desirable to have a system capability that provides customers with photographs of damaged components or parts found during incoming inspections. It would be further desirable to provide quotes for repair services, linkage to new spare parts replenishment, and inspection standardization to reduce variations between repair facilities.
BRIEF SL.TMMARY OF THE INVENTION
In one aspect, the present invention is a computerized business process that captures customer required data elements at the visual inspection process level.
The data is gathered via a network-based data capture screen and image capture workstation. The data elements include information regarding aircraft component part repair or non-repairable status, type of repair to be performed, primary non-repairable defect, and digital images of the primary non-repairable defect. The information is uploaded to a database integrated with a component repair businesses ERP
system.
The data is available for the customer to view through a secure connection to a business entity's Customer Web Center. The customer logs onto the system and accesses an Online Findings Report (OFR) to review the captured data elements and images.
In another aspect, the present invention is a system for accessing aircraft engine repair information by internal users, external customers and prospective external customers. The system includes a server, at least one computer 1 S and a network connecting computers to the server. The server is configured with a database of repair order and quote information, and includes a plurality of databases and applications associated with the repair information. The databases provide user interfaces that facilitate a user inputting and receiving information regarding aircraft engine repairs, parts replacement, quotes, and links to other new parts.
BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1 is an aviation parts and repair system diagram;
Figure 2 is a diagram showing information flow within the system of Figure 1;
Figure 3 is an exemplary embodiment of a purchase order interface;
Figure 4 is an exemplary embodiment of a shop order interface;
Figure 5 is an exemplary embodiment of a quote approval request interface;
Figure 6 is an exemplary embodiment of a quote approval interface;
COMPONENT REPAIR SERVICES
CROSS REFERENCE TO RELATED APPLICATIONS
This application claims the benefit of U.S. Provisional Application No.
60/175,178, filed January 7, 2000, which is hereby incorporated by reference in its entirety.
BACKGROUND OF THE INVENTION
This invention relates generally to customer services, and more specifically to methods and systems for accessing turbine engine aircraft components repair order information and services.
Manufacturers of aircraft engines normally provide repair and inspection services for engine and engine components. However, after an inspection of the engine has been completed, or engine component parts sent in for repair have been repaired, communicating the inspection results to engine owners, e.g.
customers, has typically been a time consuming and potentially frustrating process for both the engine manufacturer and the customer. Currently communicating inspection results from incoming inspections of aircraft engines or component parts typically involves reporting the results in tabular form, and submitting the reports to customers via mail or facsimile. In addition, variations in the inspections of different facilities is a source of customer concern.
It would be desirable to provide incoming inspection reports to customers which include information in addition to known tabular reports.
Since, customers often desire photographs of damaged components or parts found during the incoming inspections, it would be further desirable to have a system capability that provides customers with photographs of damaged components or parts found during incoming inspections. It would be further desirable to provide quotes for repair services, linkage to new spare parts replenishment, and inspection standardization to reduce variations between repair facilities.
BRIEF SL.TMMARY OF THE INVENTION
In one aspect, the present invention is a computerized business process that captures customer required data elements at the visual inspection process level.
The data is gathered via a network-based data capture screen and image capture workstation. The data elements include information regarding aircraft component part repair or non-repairable status, type of repair to be performed, primary non-repairable defect, and digital images of the primary non-repairable defect. The information is uploaded to a database integrated with a component repair businesses ERP
system.
The data is available for the customer to view through a secure connection to a business entity's Customer Web Center. The customer logs onto the system and accesses an Online Findings Report (OFR) to review the captured data elements and images.
In another aspect, the present invention is a system for accessing aircraft engine repair information by internal users, external customers and prospective external customers. The system includes a server, at least one computer 1 S and a network connecting computers to the server. The server is configured with a database of repair order and quote information, and includes a plurality of databases and applications associated with the repair information. The databases provide user interfaces that facilitate a user inputting and receiving information regarding aircraft engine repairs, parts replacement, quotes, and links to other new parts.
BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1 is an aviation parts and repair system diagram;
Figure 2 is a diagram showing information flow within the system of Figure 1;
Figure 3 is an exemplary embodiment of a purchase order interface;
Figure 4 is an exemplary embodiment of a shop order interface;
Figure 5 is an exemplary embodiment of a quote approval request interface;
Figure 6 is an exemplary embodiment of a quote approval interface;
Figure 7 is an exemplary embodiment of a non-repairables or scrap details interface;
Figure 8 is a flow chart utilized by the aircraft engine repair system;
and Figure 9 is an alternative flow chart utilized by the aircraft engine repair system.
DETAILED DESCRIPTION OF THE INVENTION
Exemplary embodiments of systems and processes that facilitate integrated network-based electronic reporting and workflow process management related to aviation component repair services are described below in detail.
The systems and processes facilitate, for example, an electronic submission of information using a client system, automated extraction of information, and web-based assessment reporting and management of components repair services information for system users.
The systems and processes are not limited to the specific embodiments described herein. In addition, components of each system and each process can be practiced independently and separately from other components and processes described herein. Each component and process also can be used in combination with other components and processes.
Figure 1 is a block diagram of a system 10 in accordance with one embodiment of the present invention. System 10 includes a server 14 and a plurality of devices 16 connected to server 14. In one embodiment, devices 16 are computers including a web browser, and server 14 is accessible to devices 16 via the Internet. In an alternative embodiment, devices 16 are servers for a network of customer devices.
Devices 16 are interconnected to the Internet through many interfaces including through a network, such as a local area network (LAN) or a wide area network (WAN), through dial-in-connections, cable modems and special high-speed ISDN lines. Alternatively, devices 16 are any device capable of interconnecting to the Internet including a web-based phone or other web-based connectable equipment.
A
database providing enclosure information is stored on server 14 and is accessible by potential customers at one of devices 16 by logging onto server 14 through one of devices 16.
System 10 is configured to provide various user interfaces whereby users and customers access repair information. Server 14 is further configured with various databases and applications to allow the user to enter repair information. The repair information is uploaded to server 14 for future retrieval. Server 14 accesses stored information and downloads the requested information to at least one of client systems 16 when the request to download is received from client system 16.
Server 14 utilizes a number of applications, described in more detail below, that reside on server 14, to store, update, retrieve and download repair information. In one embodiment, users access aircraft engine and component repair information. The databases and applications are accessed by users or customers using client system 16 configured with a standard web browser.
Server 14 is configured with databases and applications 18, 20, 22, 24, 26 and 28 that permit users and customers to access and store information regarding repairs. For example, in one embodiment, server 14 includes an online findings report (OFR) application 18, an online findings report (OFR) database 20, an order-shipping-and-billing (OSB) application 22, an inspector application 24, a new part link database 26 and a user authentication application 28, all described in more detail below. In one embodiment, server 14 and client systems 16 communicate with each other through the Internet using a TCP/IP protocol.
OFR application 18 is a computerized business process that captures customer required data elements at the visual inspection process level. The data is gathered via an intranet data capture screen and image capture workstation.
The data elements include information regarding the aircraft component part repair or non-repairable status, type of repair to be conducted, primary non-repairable defect and digital images of the primary non-repairable defect. The information is uploaded to a database integrated with the component repair businesses ERP system. The data is available for customer viewing through a secure connection to a business entity's Customer Web Center. The customer logs onto the system and accesses OFR 18 to review the captured data elements and images.
Figure 8 is a flow chart utilized by the aircraft engine repair system;
and Figure 9 is an alternative flow chart utilized by the aircraft engine repair system.
DETAILED DESCRIPTION OF THE INVENTION
Exemplary embodiments of systems and processes that facilitate integrated network-based electronic reporting and workflow process management related to aviation component repair services are described below in detail.
The systems and processes facilitate, for example, an electronic submission of information using a client system, automated extraction of information, and web-based assessment reporting and management of components repair services information for system users.
The systems and processes are not limited to the specific embodiments described herein. In addition, components of each system and each process can be practiced independently and separately from other components and processes described herein. Each component and process also can be used in combination with other components and processes.
Figure 1 is a block diagram of a system 10 in accordance with one embodiment of the present invention. System 10 includes a server 14 and a plurality of devices 16 connected to server 14. In one embodiment, devices 16 are computers including a web browser, and server 14 is accessible to devices 16 via the Internet. In an alternative embodiment, devices 16 are servers for a network of customer devices.
Devices 16 are interconnected to the Internet through many interfaces including through a network, such as a local area network (LAN) or a wide area network (WAN), through dial-in-connections, cable modems and special high-speed ISDN lines. Alternatively, devices 16 are any device capable of interconnecting to the Internet including a web-based phone or other web-based connectable equipment.
A
database providing enclosure information is stored on server 14 and is accessible by potential customers at one of devices 16 by logging onto server 14 through one of devices 16.
System 10 is configured to provide various user interfaces whereby users and customers access repair information. Server 14 is further configured with various databases and applications to allow the user to enter repair information. The repair information is uploaded to server 14 for future retrieval. Server 14 accesses stored information and downloads the requested information to at least one of client systems 16 when the request to download is received from client system 16.
Server 14 utilizes a number of applications, described in more detail below, that reside on server 14, to store, update, retrieve and download repair information. In one embodiment, users access aircraft engine and component repair information. The databases and applications are accessed by users or customers using client system 16 configured with a standard web browser.
Server 14 is configured with databases and applications 18, 20, 22, 24, 26 and 28 that permit users and customers to access and store information regarding repairs. For example, in one embodiment, server 14 includes an online findings report (OFR) application 18, an online findings report (OFR) database 20, an order-shipping-and-billing (OSB) application 22, an inspector application 24, a new part link database 26 and a user authentication application 28, all described in more detail below. In one embodiment, server 14 and client systems 16 communicate with each other through the Internet using a TCP/IP protocol.
OFR application 18 is a computerized business process that captures customer required data elements at the visual inspection process level. The data is gathered via an intranet data capture screen and image capture workstation.
The data elements include information regarding the aircraft component part repair or non-repairable status, type of repair to be conducted, primary non-repairable defect and digital images of the primary non-repairable defect. The information is uploaded to a database integrated with the component repair businesses ERP system. The data is available for customer viewing through a secure connection to a business entity's Customer Web Center. The customer logs onto the system and accesses OFR 18 to review the captured data elements and images.
OFR database 20 includes modules, described in more detail below, for organizing and storing information relating to part order and repair.
An online spare parts module (not shown) is configured to provide a searchable online catalog for spare parts and allow users to order spare parts and obtain information on those orders.
An online product support module (not shown) provides technical documentation online including, but not limited to, service bulletins, an illustrated parts catalog, engine shop manuals, standard practices manuals, engine data submittals, and fleet highlights.
An online overhaul communication module (not shown) allows customers to obtain information on their engine overhaul jobs after the engines have been submitted to the repair shop. In one embodiment, the online overhaul communication module includes a written description and digitized photos of the engine part illustrating the defect.
An online warranty module (not shown) allows customers and repair shops to submit warranty claims and view claim information online.
An online component repair module (not shown) provides two capabilities to the user. More specifically, the online component repair module includes an online catalog providing details regarding repair services offered for individual parts, and a repair order status to the user. System 10 accumulates a variety of data for numerous in-process inspection results, as well as business information that is highly confidential. Therefore, system 10 has different access levels to control and monitor the security of the system. Authorization for access is assigned by system administrators on a need-to-know basis. In an alternative embodiment, system 10 provides access based on job functions. In yet another embodiment of the invention, system 10 provides access based on position and management authority within the business entity. The editing capabilities within system 10 are also restricted to ensure that only authorized individuals have access to modify or edit the information that is already existing in the system. These system security internal controls manage and control access to the information within system 10.
An online spare parts module (not shown) is configured to provide a searchable online catalog for spare parts and allow users to order spare parts and obtain information on those orders.
An online product support module (not shown) provides technical documentation online including, but not limited to, service bulletins, an illustrated parts catalog, engine shop manuals, standard practices manuals, engine data submittals, and fleet highlights.
An online overhaul communication module (not shown) allows customers to obtain information on their engine overhaul jobs after the engines have been submitted to the repair shop. In one embodiment, the online overhaul communication module includes a written description and digitized photos of the engine part illustrating the defect.
An online warranty module (not shown) allows customers and repair shops to submit warranty claims and view claim information online.
An online component repair module (not shown) provides two capabilities to the user. More specifically, the online component repair module includes an online catalog providing details regarding repair services offered for individual parts, and a repair order status to the user. System 10 accumulates a variety of data for numerous in-process inspection results, as well as business information that is highly confidential. Therefore, system 10 has different access levels to control and monitor the security of the system. Authorization for access is assigned by system administrators on a need-to-know basis. In an alternative embodiment, system 10 provides access based on job functions. In yet another embodiment of the invention, system 10 provides access based on position and management authority within the business entity. The editing capabilities within system 10 are also restricted to ensure that only authorized individuals have access to modify or edit the information that is already existing in the system. These system security internal controls manage and control access to the information within system 10.
The architectures of system 10, as well as various components of system 10, are exemplary only. Other architectures are possible and can be utilized in connection with practicing the processes described below.
Figure 2 is a flow diagram 30 depicting the relationship among various components of system 10 shown in Figure 1. As shown in Figure 2, a user 32 accesses system 10 using client system 16 (shown in Figure 1 ) via an intranet interface 34. In an alternative embodiment, user 32 accesses system 10 via an Internet interface (not shown). In the exemplary embodiment shown in Figure 2, user 32 accesses inspection application 24 to enter information regarding aircraft engine inspection details. For example, user 32 inputs digital images of at least one of non-repairable parts, materials and quotes for repair items for storage in OFR
database 20 with linked reference to OSB database 22. However, prior to accepting any information for storage, inspection application 24 authenticates user 32 by validating the user supplied information against the pre-stored user profile in system 10 by the system administrator. The function of validation and authentication is performed by user authentication application 28 which resides on server 14. In one embodiment, inspection application 24 uses a lightweight directory access protocol (LDAP) to authenticate users 32 and customers 36. In addition, in the exemplary embodiment, a user level access permission level is required on quote approvals. An exemplary approval is an "approval button" permitting the user to provide approval authority directly through system 10. The approval button is displayed on the user interface only if user 32 has quote approval authority.
Typically customer 36 accesses system 10 at one of client systems 16 (shown in Figure 1), via an external interface 38, such as the Internet. Once customer 36 is verified as an authorized user, or alternatively registered and accepted as a new customer, access is granted to OFR application 18. Using OFR application 18, customer 36 submits queries as repair orders, including filtering criteria, by accessing OSB application 22 and OFR database 30. Using OFR application 18, purchase order details are retrieved from OSB application 22 according to particular customer details, and repair order details populated with OFR database 30. In one embodiment, filtering is date-driven. For example, as a result of filtering, purchase orders between a current date and a date three months previous are retrieved. Additionally, in other embodiments, purchase orders are sortable and viewable for customer 36 (or user 32) by purchase order receipt date, customer name, or by purchase order number.
When a purchase order is viewed, details displayed include a purchase order number, a purchase order receipt date, a shop order number, displayed as a link, a part name, part number, an image (if available), and a status of a quote for the part.
If customer 36 or user 32 selects the shop order link, a shop order screen is displayed that includes a customer name, any customer purchase order numbers, a purchase order line, a customer order (CO) line, a part name, a part number, an engine model, an engine serial number, a serial number and a quantity.
Results of an initial inspection and an initial quote are also displayed. The displayed information also includes a repair category that is one of repairable, non-repairable, salvageable, or serviceable, a scope of repair required, and a quote. All displays, described above and below, are configured to be E-mailed or printed.
Customer 36 can also select a scrap/non-repairable part from the repair details displayed. By selecting and setting search criteria, scrap details are retrieved from OFR database 20. In addition, links to details of new parts for each scrap are displayed from new and used part link database 26. When non-repairable parts are displayed, a link to display scrap details is also displayed. Scrap details include a purchase order number, a part number, a part name, a total quantity for the scrap part and a link to order new parts. For each scrap item, a digital image is displayed.
Additionally, for each scrap item, an explanation as to why the item was scrapped and a serial number of the part are also displayed. In addition, system 10 is configured to allow customer input (feedback) about OFR application 18 and associated databases.
System 10 is also configured to provide graphical reports, in the form of bar charts.
Figure 3 is an exemplary embodiment of a repair purchase order interface 50. As described above, purchase order interface 50 downloads and displays a repair purchase order number 52, a repair purchase order receipt date 54, a shop order number 56, a part name 58, part number 60, an image availability indicator 62, and a quote status 64. Also included are a search from date field 66, a search to date field 68 and a sort by field 70. The user utilizes various filter criteria to retrieve relevant data from the database. In an exemplary embodiment, selecting and clicking on shop order number 56 hypertext link, system 10 downloads and displays the subsequent user interface (not shown) that depends on the part name associated with the shop order. System 10 also provides alert messages for wrong dates inputted by _7_ the. user and guides the user to acceptable recognized values. System 10 also provides standard exception handling messages for failure of the database connection.
Figure 4 is an embodiment of an initial findings and preliminary quote interface 80, also referred to as shop order interface or component repair order S interface. Component repair order interface 80 includes a customer name 82, a repair purchase order number 84, a customer order number 86, a purchase order line 88, a CO line 90, a part name 92, a part number 94, an engine model 96, an engine serial number 98, a serial number 100 and a quantity 102. Through component repair order interface 80, system 10 downloads and displays exemplary results of an initial inspection and an initial quote. The displayed information includes a finding category 104, a repair category 106, a per unit quote 108, a total quote 110, and a part name 112. A hypertext link 114 to a non-repairables screen is also provided. By guiding the user input using component repair order interface, users 32 upload standardized inspection data to OFR database 20, thereby reducing variations in part inspections between various user inspection facilities managed by the business entity.
Figure S is an exemplary embodiment of a printable version of a quote approval request interface 120. Quote approval request interface 120 displays many of the same identification fields as described above. Also included in quote approval request interface 120 is a work scope field 122 which includes descriptions 124 of the work to be performed. A comments field 126 is provided for additional repair work descriptions.
Figure 6 is an embodiment of a quote approval interface 130 which not only includes all of the fields from printable quote approval request interface 120 (shown in Figure 5), but also includes a quote approval button 132 and a contact customer service manager button 134. Quote approval button 132 provides a user having authority the ability to approve the work. Quote approval request interface 120 provides a facility for customer approval of purchase order discrepancies and quotes.
Figure 7 is an exemplary embodiment of a non-repairables or scrap details user interface 140. Included in user interface 140 are a purchase order number 142, a part number 144, a part name 146, a quantity, 148 and a link 150 which redirects a customer to a new part order screen. For each part displayed, a thumbnail _g_ image 152 of the part to be scrapped, a serial numberl54 and a description of the inspection findings 156 is also displayed.
The above described repair information system provides customer access to critical repair information concerning aircraft engines owned by the customer. Having access to such information permits a customer to make business decisions regarding aircraft routing, cost of repairs, whether to replace or scrap parts just to name a few.
Figure 8 is a flow chart 200 utilized by aircraft engine repair system 10. Under the web-based system 10 (shown in Figure 1 ), the user accesses 210 home page of the web site through client system 16 (shown in Figure 1 ). Server system 14 (shown in Figure 1) downloads 220 and displays 230 several options. Once the user selects 240 a specific option out of various hypertext links, the request is sent to server system 14. Selecting 240 a specific option is accomplished either by click of a mouse or by a voice command. The selected option is transmitted 260 to server system 14.
Once server system 14 receives 270 a request, server system 14 accesses 280 databases and applications 18, 20, 22, 24, 26, and 28 (shown in Figure 1 ) and retrieves 290 pertinent information from databases (shown in Figure 1 ). The requested information is downloaded 292 and provided 300 to client system 14 (shown in Figure 1 ) from server 14. Server system 14 provides 300 the requested information to the user by either displaying 310 the information on the user's display or by printing 312 it to an attached or a remote printer. The user continues to search various databases for other information, updates 330 the database 20 by adding 334 folders or files, deleting 336 folders or files to database 20 with new or revised information, or exits 350 from system 10.
Updated information 354 is received 356 by server system 14 for storing 358 in appropriate databases. The user also updates 330 the database 20 by adding, deleting or modifying the information regarding a specific engine component(s). In another embodiment, client system 16, as well as server system 14, are protected from access by unauthorized individuals. As described, system 10 is an interactive searchable database 20 for all inspection & repair information and provides flexibility to users to stay current with up-to-date information. The system provides the ability for users to directly update, review and generate quotations based on current information and provide up to date information to customers for their review.
Figure 9 is yet another exemplary embodiment of a method flow chart 400 utilized by the aircraft engine repair system. The method practiced by system 10 is a method for accessing inspection and repair information by internal users and external customers using a aircraft engine repair system Method 400 improves communication and customer satisfaction. Method 400 is practiced by logging onto the system through a network. Method 400 comprises the steps of receiving inspection information. The information that is gathered is gathered via an intranet data capture screen and image capture workstation 414.
Receiving 410 inspection information includes receiving detailed visual inspection information for aircraft engine component parts submitted for repair as well as costs associated with repairing component parts by parts serial numbers.
The information received also includes at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number. Method 400 further comprises the step of updating 420 the centralized database with the received information, receiving 430 an inquiry from a customer to obtain the inspection information, and finally retrieving 440 the inspection information from the centralized database by downloading 450 the requested information in response to the inquiry. The information downloaded includes the part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number. Once the customer reviews the quote, the customer makes the decision 460 to approve or disapprove the quote. If the quote is approved 464, the customer enters the approval in system 10 thereby facilitating the authorization 468 to the business entity to proceed with the work. If the customer decides not to accept 470 the quote, the message is sent to the business entity to not to proceed with the work. In such event, the revision of the quote may be warranted.
In another embodiment of the invention, once the information is retrieved 440 from the centralized database 20 by downloading 450, the customer reviews and analyzes 480 the information since no action on the part of the customer is required. When no action is required from the customer, the retrieved information ser<res to improve communication with the customer. The customer or the internal user continues reviewing the data or exit 490 from the system. As discussed earlier, system 10 is designed to facilitate communication of inspection and repair information as well as seek approval on repair estimates through the network to expedite the process.
While the invention has been described in terms of various specific embodiments, those skilled in the art will recognize that the invention can be practiced with modification within the spirit and scope of the claims.
Figure 2 is a flow diagram 30 depicting the relationship among various components of system 10 shown in Figure 1. As shown in Figure 2, a user 32 accesses system 10 using client system 16 (shown in Figure 1 ) via an intranet interface 34. In an alternative embodiment, user 32 accesses system 10 via an Internet interface (not shown). In the exemplary embodiment shown in Figure 2, user 32 accesses inspection application 24 to enter information regarding aircraft engine inspection details. For example, user 32 inputs digital images of at least one of non-repairable parts, materials and quotes for repair items for storage in OFR
database 20 with linked reference to OSB database 22. However, prior to accepting any information for storage, inspection application 24 authenticates user 32 by validating the user supplied information against the pre-stored user profile in system 10 by the system administrator. The function of validation and authentication is performed by user authentication application 28 which resides on server 14. In one embodiment, inspection application 24 uses a lightweight directory access protocol (LDAP) to authenticate users 32 and customers 36. In addition, in the exemplary embodiment, a user level access permission level is required on quote approvals. An exemplary approval is an "approval button" permitting the user to provide approval authority directly through system 10. The approval button is displayed on the user interface only if user 32 has quote approval authority.
Typically customer 36 accesses system 10 at one of client systems 16 (shown in Figure 1), via an external interface 38, such as the Internet. Once customer 36 is verified as an authorized user, or alternatively registered and accepted as a new customer, access is granted to OFR application 18. Using OFR application 18, customer 36 submits queries as repair orders, including filtering criteria, by accessing OSB application 22 and OFR database 30. Using OFR application 18, purchase order details are retrieved from OSB application 22 according to particular customer details, and repair order details populated with OFR database 30. In one embodiment, filtering is date-driven. For example, as a result of filtering, purchase orders between a current date and a date three months previous are retrieved. Additionally, in other embodiments, purchase orders are sortable and viewable for customer 36 (or user 32) by purchase order receipt date, customer name, or by purchase order number.
When a purchase order is viewed, details displayed include a purchase order number, a purchase order receipt date, a shop order number, displayed as a link, a part name, part number, an image (if available), and a status of a quote for the part.
If customer 36 or user 32 selects the shop order link, a shop order screen is displayed that includes a customer name, any customer purchase order numbers, a purchase order line, a customer order (CO) line, a part name, a part number, an engine model, an engine serial number, a serial number and a quantity.
Results of an initial inspection and an initial quote are also displayed. The displayed information also includes a repair category that is one of repairable, non-repairable, salvageable, or serviceable, a scope of repair required, and a quote. All displays, described above and below, are configured to be E-mailed or printed.
Customer 36 can also select a scrap/non-repairable part from the repair details displayed. By selecting and setting search criteria, scrap details are retrieved from OFR database 20. In addition, links to details of new parts for each scrap are displayed from new and used part link database 26. When non-repairable parts are displayed, a link to display scrap details is also displayed. Scrap details include a purchase order number, a part number, a part name, a total quantity for the scrap part and a link to order new parts. For each scrap item, a digital image is displayed.
Additionally, for each scrap item, an explanation as to why the item was scrapped and a serial number of the part are also displayed. In addition, system 10 is configured to allow customer input (feedback) about OFR application 18 and associated databases.
System 10 is also configured to provide graphical reports, in the form of bar charts.
Figure 3 is an exemplary embodiment of a repair purchase order interface 50. As described above, purchase order interface 50 downloads and displays a repair purchase order number 52, a repair purchase order receipt date 54, a shop order number 56, a part name 58, part number 60, an image availability indicator 62, and a quote status 64. Also included are a search from date field 66, a search to date field 68 and a sort by field 70. The user utilizes various filter criteria to retrieve relevant data from the database. In an exemplary embodiment, selecting and clicking on shop order number 56 hypertext link, system 10 downloads and displays the subsequent user interface (not shown) that depends on the part name associated with the shop order. System 10 also provides alert messages for wrong dates inputted by _7_ the. user and guides the user to acceptable recognized values. System 10 also provides standard exception handling messages for failure of the database connection.
Figure 4 is an embodiment of an initial findings and preliminary quote interface 80, also referred to as shop order interface or component repair order S interface. Component repair order interface 80 includes a customer name 82, a repair purchase order number 84, a customer order number 86, a purchase order line 88, a CO line 90, a part name 92, a part number 94, an engine model 96, an engine serial number 98, a serial number 100 and a quantity 102. Through component repair order interface 80, system 10 downloads and displays exemplary results of an initial inspection and an initial quote. The displayed information includes a finding category 104, a repair category 106, a per unit quote 108, a total quote 110, and a part name 112. A hypertext link 114 to a non-repairables screen is also provided. By guiding the user input using component repair order interface, users 32 upload standardized inspection data to OFR database 20, thereby reducing variations in part inspections between various user inspection facilities managed by the business entity.
Figure S is an exemplary embodiment of a printable version of a quote approval request interface 120. Quote approval request interface 120 displays many of the same identification fields as described above. Also included in quote approval request interface 120 is a work scope field 122 which includes descriptions 124 of the work to be performed. A comments field 126 is provided for additional repair work descriptions.
Figure 6 is an embodiment of a quote approval interface 130 which not only includes all of the fields from printable quote approval request interface 120 (shown in Figure 5), but also includes a quote approval button 132 and a contact customer service manager button 134. Quote approval button 132 provides a user having authority the ability to approve the work. Quote approval request interface 120 provides a facility for customer approval of purchase order discrepancies and quotes.
Figure 7 is an exemplary embodiment of a non-repairables or scrap details user interface 140. Included in user interface 140 are a purchase order number 142, a part number 144, a part name 146, a quantity, 148 and a link 150 which redirects a customer to a new part order screen. For each part displayed, a thumbnail _g_ image 152 of the part to be scrapped, a serial numberl54 and a description of the inspection findings 156 is also displayed.
The above described repair information system provides customer access to critical repair information concerning aircraft engines owned by the customer. Having access to such information permits a customer to make business decisions regarding aircraft routing, cost of repairs, whether to replace or scrap parts just to name a few.
Figure 8 is a flow chart 200 utilized by aircraft engine repair system 10. Under the web-based system 10 (shown in Figure 1 ), the user accesses 210 home page of the web site through client system 16 (shown in Figure 1 ). Server system 14 (shown in Figure 1) downloads 220 and displays 230 several options. Once the user selects 240 a specific option out of various hypertext links, the request is sent to server system 14. Selecting 240 a specific option is accomplished either by click of a mouse or by a voice command. The selected option is transmitted 260 to server system 14.
Once server system 14 receives 270 a request, server system 14 accesses 280 databases and applications 18, 20, 22, 24, 26, and 28 (shown in Figure 1 ) and retrieves 290 pertinent information from databases (shown in Figure 1 ). The requested information is downloaded 292 and provided 300 to client system 14 (shown in Figure 1 ) from server 14. Server system 14 provides 300 the requested information to the user by either displaying 310 the information on the user's display or by printing 312 it to an attached or a remote printer. The user continues to search various databases for other information, updates 330 the database 20 by adding 334 folders or files, deleting 336 folders or files to database 20 with new or revised information, or exits 350 from system 10.
Updated information 354 is received 356 by server system 14 for storing 358 in appropriate databases. The user also updates 330 the database 20 by adding, deleting or modifying the information regarding a specific engine component(s). In another embodiment, client system 16, as well as server system 14, are protected from access by unauthorized individuals. As described, system 10 is an interactive searchable database 20 for all inspection & repair information and provides flexibility to users to stay current with up-to-date information. The system provides the ability for users to directly update, review and generate quotations based on current information and provide up to date information to customers for their review.
Figure 9 is yet another exemplary embodiment of a method flow chart 400 utilized by the aircraft engine repair system. The method practiced by system 10 is a method for accessing inspection and repair information by internal users and external customers using a aircraft engine repair system Method 400 improves communication and customer satisfaction. Method 400 is practiced by logging onto the system through a network. Method 400 comprises the steps of receiving inspection information. The information that is gathered is gathered via an intranet data capture screen and image capture workstation 414.
Receiving 410 inspection information includes receiving detailed visual inspection information for aircraft engine component parts submitted for repair as well as costs associated with repairing component parts by parts serial numbers.
The information received also includes at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number. Method 400 further comprises the step of updating 420 the centralized database with the received information, receiving 430 an inquiry from a customer to obtain the inspection information, and finally retrieving 440 the inspection information from the centralized database by downloading 450 the requested information in response to the inquiry. The information downloaded includes the part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number. Once the customer reviews the quote, the customer makes the decision 460 to approve or disapprove the quote. If the quote is approved 464, the customer enters the approval in system 10 thereby facilitating the authorization 468 to the business entity to proceed with the work. If the customer decides not to accept 470 the quote, the message is sent to the business entity to not to proceed with the work. In such event, the revision of the quote may be warranted.
In another embodiment of the invention, once the information is retrieved 440 from the centralized database 20 by downloading 450, the customer reviews and analyzes 480 the information since no action on the part of the customer is required. When no action is required from the customer, the retrieved information ser<res to improve communication with the customer. The customer or the internal user continues reviewing the data or exit 490 from the system. As discussed earlier, system 10 is designed to facilitate communication of inspection and repair information as well as seek approval on repair estimates through the network to expedite the process.
While the invention has been described in terms of various specific embodiments, those skilled in the art will recognize that the invention can be practiced with modification within the spirit and scope of the claims.
Claims (19)
1. A system for accessing inspection and repair information by internal users and external customers using a aircraft engine repair system to improve communication and customer satisfaction, said system comprising:
a device; and a server system connected to said device and configured to receive information from a user via said device, said server further configured to:
receive inspection information;
update the centralized database with the inspection information;
receive an inquiry from a customer to obtain the inspection information; and retrieve the inspection information from the centralized database in response to the inquiry.
a device; and a server system connected to said device and configured to receive information from a user via said device, said server further configured to:
receive inspection information;
update the centralized database with the inspection information;
receive an inquiry from a customer to obtain the inspection information; and retrieve the inspection information from the centralized database in response to the inquiry.
2. A system according to Claim 1 wherein said server system is further configured to:
receive detailed visual inspection information for aircraft engine component parts submitted for repair and costs associated with repairing component parts by parts serial numbers; and receive information only from the user that has been authenticated by the system based on pre-established authentication criteria.
receive detailed visual inspection information for aircraft engine component parts submitted for repair and costs associated with repairing component parts by parts serial numbers; and receive information only from the user that has been authenticated by the system based on pre-established authentication criteria.
3. A system according to Claim 2 wherein said server system is further configured to receive at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number.
4. A system according to Claim 1 wherein said server system configured to update the centralized database is further configured to:
upload the centralized database with at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number; and store the centralized database with at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number.
upload the centralized database with at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number; and store the centralized database with at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number.
5. A system according to Claim 1 wherein said server system is further configured to:
download a repair order and a quote associated with the repair order including at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number; and download hypertext links to other user interfaces for part replacement, including new spare parts.
download a repair order and a quote associated with the repair order including at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number; and download hypertext links to other user interfaces for part replacement, including new spare parts.
6. A system according to Claim 1 wherein said server system is further configured to:
upload user and customer feedback on the system;
standardize inspection data thereby reducing variations in part inspections between various user inspection facilities;
download purchase order discrepancies and a quote approval; and upload customer approval for purchase order discrepancies and quotes.
upload user and customer feedback on the system;
standardize inspection data thereby reducing variations in part inspections between various user inspection facilities;
download purchase order discrepancies and a quote approval; and upload customer approval for purchase order discrepancies and quotes.
7. A system according to Claim 1 wherein said server system is further configured to:
display various user interfaces identifying at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number;
display information in the standardized inspection data format thereby reducing variations in part inspections between various user inspection facilities; and display a quotation for the customer approval, said server system further configured to:
generate the quotation based on the inspection information stored in the centralized database; and print the quotation based on the inspection information.
display various user interfaces identifying at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number;
display information in the standardized inspection data format thereby reducing variations in part inspections between various user inspection facilities; and display a quotation for the customer approval, said server system further configured to:
generate the quotation based on the inspection information stored in the centralized database; and print the quotation based on the inspection information.
8. A system configured for accessing aircraft engine repair information by internal users, external customers and prospective external customers, said system comprising:
at least one device; and a server system connected to a database, said database containing repair order and quote information;
a secured network providing access to only authorized users based on pre-determined authentication criteria, said secured network connecting said device to said server system; and said server system configured to receive information from a user via said device, said server system further configured with a plurality of web pages associated with the repair information, said server system further configured with a user interface allowing a user to input information into the web pages for uploading the information to said server system including order placement and allowing the user to download into the web pages information from said database including quotes for repair of repairable parts and provide capability to the user to approve the quote on-line, if desired by the user to expedite the approval process.
at least one device; and a server system connected to a database, said database containing repair order and quote information;
a secured network providing access to only authorized users based on pre-determined authentication criteria, said secured network connecting said device to said server system; and said server system configured to receive information from a user via said device, said server system further configured with a plurality of web pages associated with the repair information, said server system further configured with a user interface allowing a user to input information into the web pages for uploading the information to said server system including order placement and allowing the user to download into the web pages information from said database including quotes for repair of repairable parts and provide capability to the user to approve the quote on-line, if desired by the user to expedite the approval process.
9. A method for accessing inspection and repair information by internal users and external customers using a aircraft engine repair system to improve communication and customer satisfaction, the system including a server, a centralized database, and at least one client system, said method comprising the steps of:
receiving inspection information;
updating the centralized database with the inspection information;
receiving an inquiry from a customer to obtain the inspection information; and retrieving the inspection information from the centralized database in response to the inquiry.
receiving inspection information;
updating the centralized database with the inspection information;
receiving an inquiry from a customer to obtain the inspection information; and retrieving the inspection information from the centralized database in response to the inquiry.
10. A method according to Claim 9 wherein said step of receiving inspection information further comprises the steps of:
receiving detailed visual inspection information for aircraft engine component parts submitted for repair and costs associated with repairing component parts by parts serial numbers; and receiving information only from the user that has been authenticated by the system based on pre-established authentication criteria.
receiving detailed visual inspection information for aircraft engine component parts submitted for repair and costs associated with repairing component parts by parts serial numbers; and receiving information only from the user that has been authenticated by the system based on pre-established authentication criteria.
11. A method according to Claim 10 wherein said step of receiving detailed visual inspection information further comprises the step of receiving at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number.
12. A method according to Claim 9 wherein said step of updating the centralized database with the inspection information further comprises the steps of:
uploading the centralized database with at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number; and storing the centralized database with at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number.
uploading the centralized database with at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number; and storing the centralized database with at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number.
13. A method according to Claim 9 wherein said step of retrieving the inspection information from the centralized database in response to the inquiry further comprises the steps of:
downloading a repair order and a quote associated with the repair order;
downloading hypertext links to other user interfaces for part replacement, including new spare parts.
downloading a repair order and a quote associated with the repair order;
downloading hypertext links to other user interfaces for part replacement, including new spare parts.
14. A method according to Claim 13 wherein said step of downloading the repair order and the quote further comprises the step of downloading at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number.
15. A method according to Claim 9 wherein said step of retrieving the inspection information from the centralized database in response to the inquiry further comprises the step of uploading user and customer feedback on the system.
16. A method according to Claim 9 wherein said step of retrieving the inspection information from the centralized database in response to the inquiry further comprises the step of standardizing inspection data thereby reducing variations in part inspections between various user inspection facilities.
17. A method according to Claim 9 wherein said step of retrieving the inspection information from the centralized database in response to the inquiry further comprises the steps of:
downloading a quote approval; and uploading customer approval for purchase order discrepancies and quotes.
downloading a quote approval; and uploading customer approval for purchase order discrepancies and quotes.
18. A method according to Claim 9 wherein said step of retrieving the inspection information further comprises the steps of:
displaying various user interfaces identifying at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number;
displaying information in the standardized inspection data format thereby reducing variations in part inspections between various user inspection facilities; and displaying a quotation for the customer approval, said step of displaying a quotation further comprises the steps of:
generating the quotation based on the inspection information stored in the centralized database; and printing the quotation based on the inspection information.
displaying various user interfaces identifying at least one of an aircraft component part repair status, a part non-repair status, a type of repair to be conducted, a primary non-repairable defect status including a cause of non-reparability, digital images of the primary non-repairable defect, and a quote for repairing the type of the repair by the part serial number;
displaying information in the standardized inspection data format thereby reducing variations in part inspections between various user inspection facilities; and displaying a quotation for the customer approval, said step of displaying a quotation further comprises the steps of:
generating the quotation based on the inspection information stored in the centralized database; and printing the quotation based on the inspection information.
19. A method according to Claim 9 wherein the server system and at least one client system are connected via a network, and wherein the network is one of a wide area network, a local area network, an intranet and the Internet.
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17517800P | 2000-01-07 | 2000-01-07 | |
US60/175,178 | 2000-01-07 | ||
US09/724,123 US6487479B1 (en) | 2000-01-07 | 2000-11-28 | Methods and systems for aviation component repair services |
US09/724,123 | 2000-11-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2330216A1 true CA2330216A1 (en) | 2001-07-07 |
Family
ID=26870962
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002330216A Abandoned CA2330216A1 (en) | 2000-01-07 | 2001-01-04 | Methods and systems for aviation component repair services |
Country Status (5)
Country | Link |
---|---|
US (1) | US6487479B1 (en) |
EP (1) | EP1115081A3 (en) |
JP (1) | JP2001265893A (en) |
BR (1) | BR0100152A (en) |
CA (1) | CA2330216A1 (en) |
Families Citing this family (92)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6901377B1 (en) * | 2000-01-07 | 2005-05-31 | General Electric Company | Methods and systems for aviation parts, information and services |
US7395223B1 (en) | 2000-03-31 | 2008-07-01 | Caterpillar Inc. | E-commerce based method and system for manufacturer hosting of virtual dealer stores |
JP2002002915A (en) * | 2000-06-21 | 2002-01-09 | Ebara Corp | Control method for part included in fluid machinery, ordering method for the same, and control system for the same |
US20020173885A1 (en) | 2001-03-13 | 2002-11-21 | Lowrey Larkin Hill | Internet-based system for monitoring vehicles |
US7904219B1 (en) | 2000-07-25 | 2011-03-08 | Htiip, Llc | Peripheral access devices and sensors for use with vehicle telematics devices and systems |
US7228211B1 (en) | 2000-07-25 | 2007-06-05 | Hti Ip, Llc | Telematics device for vehicles with an interface for multiple peripheral devices |
JP2002073855A (en) * | 2000-09-01 | 2002-03-12 | Nikon Corp | Product maintenance system |
JP2002095134A (en) * | 2000-09-08 | 2002-03-29 | Sumitomo Wiring Syst Ltd | Bus bar circuit and junction box provided therewith |
GB0022286D0 (en) * | 2000-09-09 | 2000-10-25 | Gb Truck Services Ltd | Vehicle Repair System |
JP3870390B2 (en) * | 2000-10-27 | 2007-01-17 | 株式会社ブロードリーフ | Recycled parts usage promotion system and recycled parts usage promotion method |
JP2002183424A (en) * | 2000-12-13 | 2002-06-28 | Matsushita Electric Ind Co Ltd | Method and system for transmitting/receiving apparatus information |
US7158978B2 (en) * | 2001-01-05 | 2007-01-02 | Goodwin Thomas R | Network method system and apparatus for recording and maintaining records |
JP2002244724A (en) * | 2001-02-20 | 2002-08-30 | Honda Motor Co Ltd | Remote monitoring device for machine and management method therefor |
US7523159B1 (en) | 2001-03-14 | 2009-04-21 | Hti, Ip, Llc | Systems, methods and devices for a telematics web services interface feature |
US6611740B2 (en) * | 2001-03-14 | 2003-08-26 | Networkcar | Internet-based vehicle-diagnostic system |
US6687652B2 (en) * | 2001-03-22 | 2004-02-03 | Sun Microsystems, Inc. | Diagnostic clearing house |
US7197482B2 (en) * | 2001-04-19 | 2007-03-27 | Honeywell International Inc. | Method and apparatus for customer storefront operations |
US6594579B1 (en) | 2001-08-06 | 2003-07-15 | Networkcar | Internet-based method for determining a vehicle's fuel efficiency |
US7457732B2 (en) * | 2001-08-17 | 2008-11-25 | General Electric Company | System and method for measuring quality of baseline modeling techniques |
US7403877B2 (en) * | 2001-08-17 | 2008-07-22 | General Electric Company | System, method and computer product for baseline modeling a product or process |
US7428478B2 (en) * | 2001-08-17 | 2008-09-23 | General Electric Company | System and method for improving accuracy of baseline models |
US7478060B2 (en) * | 2001-08-30 | 2009-01-13 | Xerox Corporation | On-site E-commerce parts ordering from products being serviced |
US20040206818A1 (en) * | 2001-12-03 | 2004-10-21 | Loda David C. | Engine-mounted microserver |
US7174243B1 (en) | 2001-12-06 | 2007-02-06 | Hti Ip, Llc | Wireless, internet-based system for transmitting and analyzing GPS data |
US6768998B2 (en) * | 2001-12-19 | 2004-07-27 | General Electric Company | Systems and methods for network-based technical library |
US8082317B2 (en) * | 2002-02-26 | 2011-12-20 | United Technologies Corporation | Remote tablet-based internet inspection system |
US6892936B2 (en) * | 2002-05-16 | 2005-05-17 | Caterpillar, Inc | Service interlink |
US20020188494A1 (en) * | 2002-05-24 | 2002-12-12 | United Technologies Corporation | Method and apparatus for managing an operation |
JP2004194129A (en) * | 2002-12-13 | 2004-07-08 | Hitachi Ltd | Video information transaction method and industrial product with video information attached thereon |
US6804589B2 (en) * | 2003-01-14 | 2004-10-12 | Honeywell International, Inc. | System and method for efficiently capturing and reporting maintenance, repair, and overhaul data |
US9520005B2 (en) | 2003-07-24 | 2016-12-13 | Verizon Telematics Inc. | Wireless vehicle-monitoring system |
US7113127B1 (en) | 2003-07-24 | 2006-09-26 | Reynolds And Reynolds Holdings, Inc. | Wireless vehicle-monitoring system operating on both terrestrial and satellite networks |
US20050043870A1 (en) * | 2003-08-22 | 2005-02-24 | General Electric Company | Method and apparatus for recording and retrieving maintenance, operating and repair data for turbine engine components |
WO2005043343A2 (en) * | 2003-11-03 | 2005-05-12 | Ps Holding, Llc | Multiple-platform estimating and automatic quoting for network-based parts resale |
US7945480B2 (en) * | 2003-11-03 | 2011-05-17 | Ps Holdings, Llc | Multiple-platform estimating and automatic quoting for network-based parts resale with transferable reports |
US7844385B2 (en) * | 2004-01-28 | 2010-11-30 | United Technologies Corporation | Microserver engine control card |
US7167788B2 (en) * | 2004-01-30 | 2007-01-23 | United Technologies Corporation | Dual-architecture microserver card |
US7613627B2 (en) * | 2004-02-02 | 2009-11-03 | Ford Motor Company | Computer-implemented method and system for collecting and communicating inspection information for a mechanism |
US7801702B2 (en) * | 2004-02-12 | 2010-09-21 | Lockheed Martin Corporation | Enhanced diagnostic fault detection and isolation |
US7584420B2 (en) * | 2004-02-12 | 2009-09-01 | Lockheed Martin Corporation | Graphical authoring and editing of mark-up language sequences |
US7734740B2 (en) * | 2004-04-16 | 2010-06-08 | The Boeing Company | Configuration management apparatus and related methods |
US7225065B1 (en) | 2004-04-26 | 2007-05-29 | Hti Ip, Llc | In-vehicle wiring harness with multiple adaptors for an on-board diagnostic connector |
US20060010152A1 (en) * | 2004-07-12 | 2006-01-12 | Snecma Services | System and method for managing machine servicing including workscope generation |
US7702435B2 (en) * | 2004-11-05 | 2010-04-20 | Honeywell International Inc. | Method and apparatus for system monitoring and maintenance |
US20080052281A1 (en) | 2006-08-23 | 2008-02-28 | Lockheed Martin Corporation | Database insertion and retrieval system and method |
US20070073602A1 (en) * | 2005-09-20 | 2007-03-29 | International Business Machines Corporation | Method, system, and program product for conditional rule-based billing with real-time error checking and for on-demand segmented labor recovery and reporting |
US20070156496A1 (en) * | 2005-12-02 | 2007-07-05 | Avery Robert L | Methods and systems for managing aircraft maintenance and material supply |
US8310533B2 (en) | 2006-03-27 | 2012-11-13 | GE Sensing & Inspection Technologies, LP | Inspection apparatus for inspecting articles |
US20080249828A1 (en) * | 2006-03-29 | 2008-10-09 | Macauley James | Method and System for Workscope Management and Control |
US8625434B2 (en) | 2006-12-29 | 2014-01-07 | Ge Inspection Technologies Lp | IP based voice communication enabled inspection system |
US8396571B2 (en) * | 2007-03-19 | 2013-03-12 | United Technologies Corporation | Process and system for multi-objective global optimization of maintenance schedules |
EP2225638B1 (en) * | 2007-11-29 | 2015-06-24 | Airbus Operations GmbH | Electronic technical logbook |
RU2463647C2 (en) * | 2007-11-29 | 2012-10-10 | Эйрбас Оперейшнс Гмбх | System and method of recording technical questions on aircraft |
US8856134B2 (en) * | 2008-05-09 | 2014-10-07 | The Boeing Company | Aircraft maintenance data retrieval for portable devices |
US8095265B2 (en) * | 2008-10-06 | 2012-01-10 | International Business Machines Corporation | Recording, storing, and retrieving vehicle maintenance records |
US20100114838A1 (en) * | 2008-10-20 | 2010-05-06 | Honeywell International Inc. | Product reliability tracking and notification system and method |
US20100198876A1 (en) | 2009-02-02 | 2010-08-05 | Honeywell International, Inc. | Apparatus and method of embedding meta-data in a captured image |
US8290802B2 (en) * | 2009-02-05 | 2012-10-16 | Honeywell International Inc. | System and method for product deployment and in-service product risk simulation |
US8266171B2 (en) * | 2009-06-11 | 2012-09-11 | Honeywell International Inc. | Product fix-effectiveness tracking and notification system and method |
US9519814B2 (en) | 2009-06-12 | 2016-12-13 | Hand Held Products, Inc. | Portable data terminal |
US8509963B1 (en) | 2009-07-23 | 2013-08-13 | Rockwell Collins, Inc. | Remote management of aircraft computer systems |
US20110276426A1 (en) * | 2010-05-05 | 2011-11-10 | Loop Aerospace Corporation | Methods and systems for facilitating aircraft parts manufacturing |
KR20130093706A (en) * | 2011-12-23 | 2013-08-23 | 한국전자통신연구원 | Apparatus for transmitting vehicle information |
US20130288210A1 (en) * | 2012-04-30 | 2013-10-31 | Andrew James Stewart | Integrated maintenance management system |
US9158834B2 (en) * | 2013-01-21 | 2015-10-13 | Snap-On Incorporated | Methods and systems for mapping repair orders within a database |
US9870444B2 (en) * | 2013-03-05 | 2018-01-16 | The Boeing Company | Shop order status visualization system |
US9340304B2 (en) | 2013-02-28 | 2016-05-17 | The Boeing Company | Aircraft comparison system |
US9612725B1 (en) | 2013-02-28 | 2017-04-04 | The Boeing Company | Nonconformance visualization system |
US9110560B1 (en) * | 2013-02-28 | 2015-08-18 | The Boeing Company | Shop order status visualization system |
US10481768B2 (en) * | 2013-04-12 | 2019-11-19 | The Boeing Company | Nonconformance identification and visualization system and method |
US10067650B2 (en) * | 2013-06-20 | 2018-09-04 | The Boeing Company | Aircraft comparison system with synchronized displays |
US10061481B2 (en) | 2013-02-28 | 2018-08-28 | The Boeing Company | Methods and devices for visually querying an aircraft based on an area of an image |
US9492900B2 (en) | 2013-03-15 | 2016-11-15 | The Boeing Company | Condition of assembly visualization system based on build cycles |
US9292180B2 (en) | 2013-02-28 | 2016-03-22 | The Boeing Company | Locator system for three-dimensional visualization |
US9182892B2 (en) | 2013-02-28 | 2015-11-10 | The Boeing Company | Condition of assembly visualization system |
US9880694B2 (en) | 2013-05-09 | 2018-01-30 | The Boeing Company | Shop order status visualization system |
US20140298216A1 (en) | 2013-03-28 | 2014-10-02 | The Boeing Company | Visualization of an Object Using a Visual Query System |
US10416857B2 (en) * | 2013-05-09 | 2019-09-17 | The Boeing Company | Serial number control visualization system |
JP6355909B2 (en) * | 2013-10-18 | 2018-07-11 | 三菱重工業株式会社 | Inspection record apparatus and inspection record evaluation method |
EP2990894B1 (en) * | 2014-08-25 | 2018-09-26 | The Boeing Company | Serial number control visualization system |
US20160132893A1 (en) * | 2014-11-12 | 2016-05-12 | Donald Lee Bisges | System and method for returned goods management |
US11144888B2 (en) | 2015-10-02 | 2021-10-12 | Snap-On Incorporated | Method and system for augmenting real-fix tips with additional content |
US11429936B2 (en) | 2015-10-02 | 2022-08-30 | Snap-On Incorporated | System and method for dynamically-changeable displayable pages with vehicle service information |
US10685147B2 (en) | 2016-02-29 | 2020-06-16 | The Boeing Company | Non-conformance mapping and visualization |
US10812605B2 (en) | 2017-02-10 | 2020-10-20 | General Electric Company | Message queue-based systems and methods for establishing data communications with industrial machines in multiple locations |
DE102018108748A1 (en) * | 2017-04-14 | 2018-10-18 | Gulfstream Aerospace Corporation | SYSTEM AND METHOD FOR PROVIDING A VIRTUAL AIRCRAFT CONSTRUCTION PROCESS |
US10364049B2 (en) * | 2017-12-13 | 2019-07-30 | The Boeing Company | Supporting maintenance of aircraft |
CN112352287A (en) * | 2018-06-18 | 2021-02-09 | 皇家飞利浦有限公司 | Part co-replacement recommendation system for field service of medical imaging system |
DE102018118471A1 (en) * | 2018-07-31 | 2020-02-06 | Airbus Operations Gmbh | Device and method for providing spare parts for an aircraft |
US10974851B2 (en) | 2018-11-09 | 2021-04-13 | Textron Innovations Inc. | System and method for maintaining and configuring rotorcraft |
CN111027720A (en) * | 2019-08-16 | 2020-04-17 | 中国人民解放军69007部队 | Novel equipment for integrated construction and realization of maintenance support information platform |
CN113282438B (en) * | 2021-04-19 | 2023-07-07 | 中国航发沈阳发动机研究所 | Remote maintenance method and system for test bed software of aero-engine |
Family Cites Families (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4404639A (en) * | 1980-12-02 | 1983-09-13 | Chevron Research Company | Automotive diagnostic system |
US4567359A (en) * | 1984-05-24 | 1986-01-28 | Lockwood Lawrence B | Automatic information, goods and services dispensing system |
US5414626A (en) * | 1993-05-19 | 1995-05-09 | Envirotest Systems Corp. | Apparatus and method for capturing, storing, retrieving, and displaying the identification and location of motor vehicle emission control systems |
US5552987A (en) | 1994-07-20 | 1996-09-03 | Barger; Randall R. | Aircraft engine cycle logging unit |
US5717595A (en) * | 1995-01-12 | 1998-02-10 | Cherrington; John K. | Integrated automated vehicle analysis |
US5729452A (en) * | 1995-03-31 | 1998-03-17 | Envirotest Acquisition Co. | Method and system for diagnosing and reporting failure of a vehicle emission test |
EP0770967A3 (en) | 1995-10-26 | 1998-12-30 | Koninklijke Philips Electronics N.V. | Decision support system for the management of an agile supply chain |
WO1997018661A1 (en) | 1995-11-13 | 1997-05-22 | Answersoft, Inc. | Intelligent information routing system and method |
US5963915A (en) * | 1996-02-21 | 1999-10-05 | Infoseek Corporation | Secure, convenient and efficient system and method of performing trans-internet purchase transactions |
DE19615008A1 (en) * | 1996-04-16 | 1997-10-23 | Maha Gmbh & Co Kg | Method and device for controlling a test lane system for motor vehicles |
US5931877A (en) * | 1996-05-30 | 1999-08-03 | Raytheon Company | Advanced maintenance system for aircraft and military weapons |
US5808907A (en) * | 1996-12-05 | 1998-09-15 | Caterpillar Inc. | Method for providing information relating to a mobile machine to a user |
US5960196A (en) * | 1996-12-18 | 1999-09-28 | Alcatel Usa Sourcing, L.P. | Software release metric reporting system and method |
US6115656A (en) * | 1997-06-17 | 2000-09-05 | Mcdonnell Douglas Corporation | Fault recording and reporting method |
US6003808A (en) * | 1997-07-11 | 1999-12-21 | Pratt & Whitney Canada Inc. | Maintenance and warranty control system for aircraft |
US6052631A (en) * | 1997-08-08 | 2000-04-18 | Management Systems Data Service, Inc. ("Msds, Inc.") | Method and system for facilitating vehicle inspection to detect previous damage and repairs |
US6263268B1 (en) * | 1997-08-26 | 2001-07-17 | Transcontech Corporation | System and method for providing mobile automotive telemetry |
US5970475A (en) * | 1997-10-10 | 1999-10-19 | Intelisys Electronic Commerce, Llc | Electronic procurement system and method for trading partners |
US6151601A (en) * | 1997-11-12 | 2000-11-21 | Ncr Corporation | Computer architecture and method for collecting, analyzing and/or transforming internet and/or electronic commerce data for storage into a data storage area |
US6314422B1 (en) * | 1997-12-09 | 2001-11-06 | Chrysler Corporation | Method for softlinking between documents in a vehicle diagnostic system |
US6233577B1 (en) * | 1998-02-17 | 2001-05-15 | Phone.Com, Inc. | Centralized certificate management system for two-way interactive communication devices in data networks |
US7668782B1 (en) * | 1998-04-01 | 2010-02-23 | Soverain Software Llc | Electronic commerce system for offer and acceptance negotiation with encryption |
US6263322B1 (en) * | 1998-07-07 | 2001-07-17 | Hunter Engineering Company | Integrated automotive service system and method |
US6067486A (en) | 1999-02-01 | 2000-05-23 | General Electric Company | Method and system for planning repair of an aircraft engine |
US6330499B1 (en) * | 1999-07-21 | 2001-12-11 | International Business Machines Corporation | System and method for vehicle diagnostics and health monitoring |
US6263265B1 (en) * | 1999-10-01 | 2001-07-17 | General Electric Company | Web information vault |
US6338152B1 (en) * | 1999-10-28 | 2002-01-08 | General Electric Company | Method and system for remotely managing communication of data used for predicting malfunctions in a plurality of machines |
US6321142B1 (en) * | 2000-05-16 | 2001-11-20 | Cummins Engine Company, Inc. | System for programming a vehicle control computer with selectable features and/or trim values |
US6308120B1 (en) * | 2000-06-29 | 2001-10-23 | U-Haul International, Inc. | Vehicle service status tracking system and method |
-
2000
- 2000-11-28 US US09/724,123 patent/US6487479B1/en not_active Expired - Fee Related
-
2001
- 2001-01-04 CA CA002330216A patent/CA2330216A1/en not_active Abandoned
- 2001-01-05 EP EP01300091A patent/EP1115081A3/en not_active Withdrawn
- 2001-01-05 JP JP2001000298A patent/JP2001265893A/en not_active Withdrawn
- 2001-01-08 BR BR0100152-3A patent/BR0100152A/en not_active IP Right Cessation
Also Published As
Publication number | Publication date |
---|---|
US6487479B1 (en) | 2002-11-26 |
EP1115081A3 (en) | 2004-01-02 |
BR0100152A (en) | 2001-08-28 |
EP1115081A2 (en) | 2001-07-11 |
JP2001265893A (en) | 2001-09-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6487479B1 (en) | Methods and systems for aviation component repair services | |
US6901377B1 (en) | Methods and systems for aviation parts, information and services | |
US7127409B2 (en) | Methods and systems for aviation nonconformance component management | |
US7941744B2 (en) | System and method for electronic document generation and delivery | |
US6804589B2 (en) | System and method for efficiently capturing and reporting maintenance, repair, and overhaul data | |
US8374970B2 (en) | Apparatus, systems and methods for online, multi-parcel, multi-carrier, multi-service enterprise parcel shipping management | |
US20020095347A1 (en) | Network-based method and system for selecting shipping carrier | |
US20040024662A1 (en) | Equipment documentation management system, method, and software tools | |
US20020111850A1 (en) | System and method for new product clearance and development | |
US20020107749A1 (en) | Networked based paralleling switchgear equipment configuration process | |
US20020194090A1 (en) | Method and system for obtaining information utilizing user interfaces | |
US20100125464A1 (en) | System and Method for Entering a List of Insured Items for Valuation | |
US20080027826A1 (en) | Method, system and computer program product for facilitating the telecommunication equipment ordering process | |
US6785692B2 (en) | Systems and methods for coordinating QA events | |
US20020091540A1 (en) | Method and system for emergency assistance management | |
WO2001020514A1 (en) | Method, apparatus, and system for facilitating transactions between vendors and purchasers | |
US20020069164A1 (en) | Method and system for saving and recalling bill of material information | |
CA2360906C (en) | Method for mapping information from a network-based data source | |
CA2422546A1 (en) | Systems and methods for managing treasury trade requests | |
AU728124B3 (en) | A claims system | |
JP2002312646A (en) | Edi ordering and order acceptance system and edi adaptive production control system | |
JP2002109257A (en) | Server and terminal for supporting article order approval processing, server for supporting delivered article check processing, server for supporting article maintenance request processing, article order approval processing supporting method, delivered article check processing supporting method, article maintenance request processing supporting method and computer readable storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
FZDE | Discontinued |