Computer-implemented method and system for collecting and communicating inspection information for a mechanism
A method for collecting and communicating inspection information for a vehicle is provided. The method comprises electrically transmitting repair order information from an original electronic repair order to initiate a repair on the vehicle. The repair order information designates a technician to perform the repair. The method further comprises electronically receiving a notification to indicate that the technician received the repair order information and electronically generating an electronic inspection form including a questionnaire for the technician to input inspection information in response to the notification. The method further comprises electronically receiving into the electronic inspection form the inspection information and determining that the electronic inspection form is complete based on whether at least one of the electronic inspection form has been generated and the inspection information is received.
Latest Ford Patents:
This application is a continuation of U.S. application Ser. No. 10/770,145 filed on Feb. 2, 2004, which is hereby incorporated by reference in its entirety.
REFERENCE TO A COMPUTER PROGRAM LISTING APPENDIXThis application includes a computer program listing appendix submitted on two compact discs and is incorporated into the specification by reference. Each compact disc includes the following files: computer listing 1.txt; computer listing 2.txt; computer listing 3.txt; computer listing 4.txt; computer listing 5.txt; and computer listing 6.txt.
BACKGROUND1. Technical Field
One aspect of the present invention relates generally to a computer-implemented method and system for collecting and communicating inspection information for a mechanism, and more specifically, an automobile.
2. Background Art
For generations, vehicle owners have been visiting repair centers or dealerships for repair work. In general, the customer arrives at the repair center or dealership to be greeted by a vehicle service advisor, which attends to the customer's immediate repair needs. With the proliferation of computers, the vehicle service advisor often inputs repair and vehicle information into a computerized repair form and prints a hard copy of the form upon completion. The hard copy is handed over to a technician who performs the repair work.
Often, the technician will also conduct a vehicle inspection while the customer's automobile is being serviced or repaired. Recently, the vehicle inspection has become focused and streamlined with the advent of paper inspection checklists, as exemplified by
However, the non-automated and non-integrated process outlined has its drawbacks. For example, the completed checklist may not be given to the service advisor until after the vehicle has been serviced, or even after the customer has left the repair center with the repaired vehicle. Moreover, technicians may by-pass completing the checklist because completion is not tracked. Consequently, the service advisor misses an opportunity to convey additional service needs to the customer while they wait for their vehicle to be repaired. Moreover, the service advisor sometimes neglects to apprise the customer of additional service needs based on the inspection report. Further, inspection information is commonly lost since the information is collected on paper, instead of electronically. Yet other information pertaining to the repair process may not be collected, for example, information relevant to specific service advisors and technicians. Due to the communication gap and information loss, managers can have difficulty tracking the performance of their service advisors and technicians. Moreover, repair centers may miss an opportunity to provide return customers service information relating to a prior inspection or future repair needs not apparent the day of the repair.
The above-identified process can also lead to inefficiencies. Namely, the technician often has to leave the repair/inspection area to deliver the repair form to the service advisor. This additional step takes the technician away from his/her core task of repairing the vehicle.
Due to the disadvantages of the conventional method and system, there exists a need to provide an automated and integrated computer-implemented method and system for collecting and communicating inspection information for a mechanism, and more specifically, a vehicle. Moreover, there exists a need to provide an automated and integrated computer-implemented method and system for tracking and resolving customer concerns relating to the dealership experience. Furthermore, there exists a need to provide an automated and integrated computer-implemented method and system for conducting and tracking follow-up relating to a customer's dealership experience.
SUMMARYIn one embodiment, a method for collecting and communicating inspection information for a vehicle is provided. The method comprises electrically transmitting repair order information from an original electronic repair order to initiate a repair on the vehicle. The repair order information designates a technician to perform the repair. The method further comprises electronically receiving a notification to indicate that the technician received the repair order information and electronically generating an electronic inspection form including a questionnaire for the technician to input inspection information in response to the notification. The method further comprises electronically receiving into the electronic inspection form the inspection information and determining that the electronic inspection form is complete based on whether at least one of the electronic inspection form has been generated and the inspection information is received.
One embodiment of the present invention is an automated and computer-implemented method for collecting and communicating inspection information for a mechanism. The method includes receiving repair order information from a repair order, generating an electronic inspection form, including a questionnaire for inputting inspection information, receiving inspection information which is input into the questionnaire of the electronic inspection form, and transmitting at least a portion of each of the inspection information and the repair information to cause the repair order to be appended with the transmitted information to obtain an appended repair order. The information contained on the appended repair order is suitable for communication to an individual requesting repair of the mechanism.
Accordingly,
Computer system 10 can include an organized sub-network architecture, as depicted by boxes 11, 12 and 13. Box 11 represents a dealership infrastructure consisting of dealer computer 12, SM server 24 and SM database 26. Box 12 represents a first level security layer, commonly referred to as a demilitarized zone or a gate keeping zone, typical of organizations utilizing the public Internet to communicate with external partners and/or customers, which includes web server 14, landing server 20, and network connections. Box 13 represents a manufacturer sub-network, which includes application server 16, proxy server 18, and network connections.
Application server 16 can communicate with database 28. Server 16 can utilize database 28 to search and retrieve a collection of data organized in database 28. Application server 16 is configured to operably execute one or more computer modules 30 for use by computer system 10. Non-limiting examples of computer modules include, a report card module, a concern prevention and resolution (CP&R) module, and a follow-up module. These modules are described in greater detail below.
Computer 12 and servers 14, 16, 18, 20, 22 and 24 can communicate with one another through network connections and protocols. Dealer computer 12 can be in communication with web server 14 such that outbound requests and inbound responses can be received and transmitted, respectively, by computer 12 and web server 14. Web server 14 can be in communication with application server 16 such that outbound requests and inbound responses can be received and transmitted, respectively, by servers 14 and 16, through a port connection, utilizing a TCP-IP communication protocol via the Internet, including XML. Application server 16 can be in communication with proxy server 18 such that outbound requests can be transmitted by server 16 to server 18, through the use of Http protocol.
Proxy server 18 can transmit an inbound response to web server 24 using http protocol with a persistent cookie. Further, proxy server 18 can transmit an outbound request to extranet server 22, which in turn transmits a request to SM server 24. SM server 24 can access SM database 26 to retrieve data requested. Landing server 20 can transmit an inbound response to proxy server 18, using http protocol. Extranet server 22 can transmit an inbound response to landing server 20, using http protocol. It should be understood that depending on the embodiment, the communications described above can be executed using TCP-IP communication protocol via the Internet, including XML.
Block flow diagram 32 represents a method of utilizing a report card module, residing on application server 16, for collecting and communicating inspection information for a mechanism. The report card module can be web-based, utilizing the Internet and a number of graphical user interfaces (GUIs) to communicate with an individual or entity that triggers the collection and communication of inspection information. For example, an individual or entity may trigger the process by requesting repair of a mechanism. An example of a mechanism includes, but is not limited to an automobile. However, it should be understood that other mechanisms are contemplated by the present invention as long as they are capable of being repaired and inspected. Non-limiting examples include automotive systems (e.g. a brake system, a transmission, or engine), snowmobiles, airplanes, and heavy machinery. Users of the report card module include, but are not limited to, individuals and entities (otherwise referred to as customers) requesting repair or inspection and repair center employees, for example, technicians, service advisors, and service managers.
According to one embodiment of the present invention, a process utilizing the report card module begins with a customer arriving at a repair center so that repair work can be performed on the customer's automobile, as depicted in block 34 of
In certain embodiments, a XML package is transmitted to SM server 24 using computer system 10 to validate and append to the electronic repair order. Listing 1 and 2 included on the computer program listing appendix contain example of a XML package for validating and appending to the electronic repair order, respectfully. It should be understood that the content, arrangement and language of the generic request XML package of Listings 1 and 2 can be rearranged, modified and/or supplemented to best fit the communication between SM server 24 and application server 16. The service advisor also enters information relating to the customer and the purpose of the visit. For instance, the purpose of the visit can be a lubrication, oil and filter service.
Once the data entry is completed, the service advisor prints out a hard copy of the electronic repair order and has the customer sign it. As depicted in block 38, the repair order is delivered to a technician. Upon receiving a repair order, the technician begins the process of entering information into an electronic report card form, as depicted in block 40. It should be understood that the technician also starts to work on the repair(s) requested by the customer. In certain embodiments, the technician uses a hand-held computer device to perform the data entry. It should be understood that other computer devices can also be utilized, including, but not limited to, a desktop computer, a notebook computer, and a personal digital assistant (PDA).
The report card module generates a logon GUI for display on the hand-held computer. The logon GUI includes data entry fields for a userid and password and a “next” button for transmitting the contents of the data entry fields to the report card module for verification. After verification, the report card module generates an employee number GUI for display on the hand-held computer. The employee number GUI includes a data entry field for an employee number and a “next” button for transmitting the contents of the data entry field to the report card module for verification. The employee number can be used to track metric values for specific technicians. Upon verification, the technician is prompted to enter a repair order number, which appears on the hard copy of the electronic repair order. The report card module verifies that the repair order is valid and assigned to the employee having the employee number already entered.
After verification, an electronic report card form is generated by the report card module and displayed on the hand-held computer.
Input section 104 includes an “every 5,000 (or 3,000) mile” sub-section 106, an “every 15,000 miles” sub-section 108, an “every 30,000 miles” sub-section 110, a “tire inspection” sub-section 112, a “battery performance” sub-section 114, a “brake inspection” sub-section 116, and a “general comments” sub-section 118. Each sub-section 106 through 116 includes a number of inspection items. Each inspection item is tied either to a color-coded or non-color-coded selection area. In certain embodiments, the color-coded section includes green, yellow, and red sections. Green indicates that the technician has inspected the item and it does not need further attention. Yellow indicates that since there is some wear on an inspected part, repair work will be needed in the near future. For instance, if a technician inspects the brakes and sees that they are fine now, but will need work in the near future, the technician would select the button in the yellow area. Red indicates that an inspected part needs immediate attention. For instance, if a customer came in for an oil change, and in the process of the inspection, the technician discovers very serious tire wear, then the technician would select the button in the red area. In certain embodiments, the non-color coded sections include two radio buttons, one for an “OK” level and one for an “ADD” level.
Sub-section 106 includes, but is not limited to, the following inspection items: washer fluid, transmission fluid, brake fluid, power steering fluid, coolant, clutch/axle fluid for trucks, horn, lamps, signals, washer, wipers, blades, windshield, hoses, fluid leaks, CV axle boots, exhaust system, drive shaft, shift linkage, steering, linkages, and suspension. Sub-section 108 includes, but is not limited to, brake system and cooling system. Sub-section 110 includes, but is not limited to, drive belt(s), battery terminals, clutch operation, and evaporative system. Sub-section 112 includes, but is not limited to, tread depth and wear pattern/damage for each tire, and tire pressure. Sub-section 114 includes, but is not limited to, radio buttons for the status of the battery (good, recharge, and bad). Sub-section 116, includes, but is not limited to, disc and drum measurements for the left front, right front, left rear, and right rear brakes. Sub-section 118 allows the technician to enter general comments about the inspection.
In certain embodiments, the following items are considered required, i.e. failure to check all these items results in an error message: washer fluid, transmission fluid, brake fluid, power steering fluid, coolant, clutch/axle fluid for trucks, horn, lamps, signals, washer, wipers, blades, windshield, hoses, fluid leaks, CV axle boots, exhaust system, drive shaft, shift linkage, steering, linkages, suspension, tread depth and wear pattern/damage for each tire, tire pressure, disc and drum measurements for the left front, right front, left rear, and right rear brakes.
GUI 100 also includes “cancel” button 120, “save” button 122, and “complete report card” button 124. “Cancel” button 120 can be utilized if the technician is informed that the inspection is not necessary. “Save” button 122 can be utilized in the technician is pulled away from filling out the electronic form in favor of another activity. “Complete report card” button 124 can be utilized once the report card form is completed.
Once the technician clicks on “complete report card” button 124, an e-mail or electronic notification containing the report card inspection information can be sent to the service advisor's e-mail address. In certain embodiments, an e-mail alert or electronic notification is sent if the inspection identified concerns, e.g., any yellow or red conditions, as depicted in decision block 42 and block 44 of
Advantageously, the service advisor can immediately contact the customer after receiving and reviewing the e-mail or electronic notification to recommend additional service based on the inspection results, as depicted in block 46 of
As depicted in blocks 45, 47 and 48 of
Additionally, data regarding the additional repair item(s) can be stored in SM database 26 for reporting and analysis purposes as depicted in blocks 45 and 48 of
As depicted in block 49 of
Block flow diagram 50 represents a method of utilizing a concern prevention and resolution (“CP&R”) module, residing on application server 16, for tracking and resolving customer concerns relating to a customer's dealership experience. The CP&R module provides a computer-implemented tool for managing customer, contacts.
In block 52, a customer contact is created by the CP&R module. The customer contact can be created based on various reasons. For instance, a customer's response to a sales and/or service survey may not meet dealer-specified score levels. Alternatively, the customer contact can be generated because additional customer comments are noted in additional comments area of an electronic follow-up form. Further, a dealership employee can manually enter a customer contact.
Once a customer contact is created, an e-mail or electronic notification is transmitted to a customer relations manager (CRM), as depicted in block 54. As depicted in block 56 and 58, the CP&R module can allow a CRM or supervisor to assign a customer contact to an individual for action. When an individual is assigned a contact, that individual can receive an e-mail notice or electronic notification, containing an ID for the contact.
The CP&R can generate a contact list GUI, which displays contact(s) assigned to an individual. The contact list GUI can be displayed upon an individual's request.
An individual can click on the contact icon to display a contact information GUI, generated by the CP&R module.
Contact summary window 164 displays contact information, including, but not limited to, contact date, department involved, and individual assigned to contact. In block 58 of
According to contact detail window 166, the action requested is “CONTACT CUSTOMER FOR ADDITIONAL INFORMATION”. In this example, the individual contacts the customer to resolve the issue, as depicted by block 60 of
Advantageously, the CP&R module collects information for use in tracking and analyzing the CP&R process. For example, the CP&R module automatically track the individual that is assigned to a contact for resolution handling. Additionally, the CP&R module can track the status of the contact. The CP&R module also tracks the average number of days to resolve a contact from its origination date, generating a customer concern file based on one or more answers, failing to meet the one or more standards on a first date, receiving information from the customer regarding the concern transmitting the information to the customer concern file, and transmitting the customer concern file to a concern resolution individual or entity, the customer information being used to resolve the customer concern.
Block flow diagram 70 of
As depicted in block 72, contact is initiated with an individual after a dealership experience, for example, completion of repairs requested by the customer. A follow-up person can utilize the follow-up module to obtain sales and service follow-up call requests for processing. In certain embodiments, XML packages are transmitted to SM server 24 to retrieve sales and service follow-up call requests. Computer listings 5 and 6 are examples of XML packages for retrieving sales and service follow-up call requests, respectfully. As depicted in block 74, feedback is received by the customer after contact is initiated. The contact initiation and feedback collection can be accomplished by the system through an e-mail survey, a follow-up person, follow-up agency, or surveyor, either employed or not employed by a dealership.
In certain embodiments, the contact can be initiated via a telephone call. If the customer agrees to participate in a follow-up survey, the service follow-up person can ask the customer a number of questions, which are contained on an electronic survey document, viewable from a web browser or word processing application. The electronic survey document can include one or more input boxes for inputting answers given to survey questions. Depending on the answers, the follow-up person is directed to the next question on the electronic document.
For example, the follow-up person can ask the individual to rate an experience based on a range (low to high) or yes/no questions. For instance, the individual can be asked “were you greeted by our service staff within two minutes of your arrival?” If the individual answers affirmatively, the electronic survey document prompts the follow-up person to ask another question. If the individual answers negatively, the electronic survey document may prompt the follow-up person to ask different question, addressing the negative response.
In other embodiments, the contact can be initiated by automatically transmitting a survey to a customer's e-mail address. This alternative may be utilized if data stored in the SM server 24 indicates that the customer prefers e-mail contact. The e-mail contains a request to conduct a survey via a web link that is provided. Once the individual clicks on the web link, a survey GUI generated by the follow-up module and hosted by application server 16 is displayed for completing the survey.
In either case described above, telephone or e-mail contact, a dealer can identify a trigger value wherein a customer's response may trigger the follow-up module to automatically generate a customer contact file that is transmitted to the CP&R module for further processing and resolution. For example, any dissatisfaction may trigger the generation of a customer contact file.
As depicted by block 76, the follow-up module can determine a value for a metric based on the individual feedback and other information collected during the follow-up process. In certain situations, pre-selected thresholds for individual customer response will be met as shown in decision 78 of
While the best mode for carrying out the invention has been described in detail, those familiar with the art to which this invention relates will recognize various alternative designs and embodiments for practicing the invention as defined by the following claims.
Claims
1. A method for collecting and communicating inspection information for a vehicle, the method comprising:
- electrically transmitting repair order information from an original electronic repair order to initiate a repair on the vehicle, the repair order information designating a technician to perform the repair;
- electronically receiving a notification to indicate that the technician received the repair order information;
- electronically generating an electronic inspection form including a questionnaire for the technician to input inspection information in response to the notification;
- electronically receiving into the electronic inspection form the inspection information; and
- determining that the electronic inspection form is complete based on whether at least one of the electronic inspection form has been generated and the inspection information is received.
2. The method of claim 1 further comprising generating a count for the technician indicating that the electronic inspection form is complete in response to determining that the at least one of the electronic inspection form has been generated and the inspection information is received.
3. The method of claim 2 further comprising executing the steps of (i) electrically transmitting the repair order information from an original electronic repair order to initiate a repair on the vehicle; (ii) electronically receiving the notification; (iii) electronically generating the electronic inspection form; (iv) electronically receiving into the electronic inspection form the inspection information; and (v) determining that the electronic inspection form is complete one or more times.
4. The method of claim 3 further comprising incrementing the count for the technician to generate a technician based metric corresponding to a number of electronic inspection forms processed with a complete inspection each time it is determined that the at least one of the electronic inspection form has been generated and the inspection information is received.
5. The method of claim 1 wherein the notification corresponds to a repair order number that is associated with the original repair order.
6. The method of claim 1 wherein electronically receiving into the electronic inspection form the inspection information further comprises causing the original electronic repair order to be appended with at least a portion of the inspection information to obtain an electronic appended order.
7. The method of claim 6 further comprising determining whether the electronic appended order is available to print.
8. The method of claim 7 further comprising executing the steps of causing the original electronic repair order to be appended with the at least a portion of the inspection information to obtain the electronic appended order and determining whether the electronic appended order is available to print one or more times.
9. The method of claim 8 further comprising determining a value for a cashier based metric which corresponds to a number of printed electronic appended repair orders based on the number of times the steps of causing the original electronic repair order to be appended with the at least a portion of the inspection information to obtain the electronic appended repair order and determining whether the electronic appended repair order is available to print are executed.
10. A computer-implemented method for collecting and communicating inspection information for a mechanism, the method comprising:
- electronically transmitting repair order information from an original electronic repair order to initiate a repair on the mechanism;
- electronically generating an electronic inspection form including a questionnaire for inputting inspection information;
- electronically receiving the inspection information;
- causing the original electronic repair order to be appended with at least a portion of the received inspection information to obtain an electronic appended repair order;
- determining whether the electronic appended repair order is available to print;
- executing the steps of causing the original electronic repair order to be appended with the at least a portion of the received inspection information and determining whether the electronic appended repair order is available to print one or more times; and
- determining a value for a cashier based metric which corresponds to a number of printed electronic appended repair orders based on the number of times the steps of causing the original electronic repair order to be appended with the at least a portion of the received inspection information and determining whether the electronic appended repair order is available to print is executed.
11. The method of claim 10 wherein the repair order information designating a technician to perform the repair.
12. The method of claim 11 further comprising electronically receiving a notification to indicate that the technician received the repair order information prior to electronically generating the electronic inspection form.
13. The method of claim 12 wherein electronically generating the electronic inspection form further comprises electronically generating the electronic inspection form including a questionnaire for the technician to input inspection information in response to the notification.
14. The method of claim 13 further comprising determining that the electronic inspection form is complete based on whether the at least one of the electronic inspection form has been generated and the inspection information is received.
15. The method of claim 14 further comprising generating a count for the technician indicating that the electronic inspection form is complete in response to determining that the at least one of the electronic inspection form has been generated and the inspection information is received.
16. A method comprising:
- electronically transmitting repair information from an original repair order, the repair information designating a technician to perform a repair on a vehicle;
- receiving an electronic notification to indicate that the technician received the repair information;
- generating an electronic inspection form in response to the electronic notification; and
- determining that the electronic inspection form is complete based on whether the electronic inspection form is generated.
17. The method of claim 16 wherein the electronic inspection form includes a questionnaire for the technician to input inspection information.
18. The method of claim 17 further comprising electronically receiving into the electronic inspection form the inspection information.
19. The method of claim 18 further comprising determining that the electronic inspection form is complete based on whether the inspection information is received.
20. The method of claim 19 further comprising generating a count for the technician indicating that the electronic inspection form is complete in response to determining that the at least one of the electronic inspection form has been generated and the inspection information is received.
Type: Application
Filed: Sep 24, 2009
Publication Date: Feb 4, 2010
Applicant: Ford Motor Company (Dearborn, MI)
Inventors: Dennis Doyle (Northville, MI), Michael Benakovich (New Johnsonville, TN), Kevin Santer (Plymouth, MI), John Graham (Plymouth, MI), Joe Retzbach (Novi, MI)
Application Number: 12/586,574
International Classification: G06Q 10/00 (20060101); G06F 15/16 (20060101);