Method and system for providing vehicle maintenance reminders

Abstract

A method performed by a first computing system includes receiving a message identifying a symptom of a first vehicle from a second computing system; and sending a maintenance reminder to the second computing system. The maintenance reminder includes a first phrase describing a first process performed on a second vehicle presenting the symptom, wherein the first process performed on the second vehicle produces a result insufficient to determine that a component of the second vehicle associated with the symptom is defective. The maintenance reminder also includes a second phrase describing a second process performed on a given vehicle, wherein the given vehicle is (i) the second vehicle or (ii) a third vehicle also presenting the symptom, wherein the second process performed on the given vehicle produces a result sufficient to determine that a component of the given vehicle associated with the symptom is defective.

Description

[0001] This application is a divisional application of the Chinese invention patent application with the application date of November 10, 2016, application number 201680065999.5, and invention name “Method and system for providing vehicle maintenance reminders”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. Patent Application No. 14 / 938,662, filed on November 11, 2015, which is incorporated herein by reference in its entirety. Background Art

[0004] Many products produced by manufacturers must occasionally be repaired. Many owners are not equipped or otherwise unable to repair certain products. These owners can rely on professional repair technicians to service or repair the owner's product.

[0005] Product manufacturers use significant resources (eg, human and financial) to generate repair information, such as repair manuals and technical service bulletins, that repair technicians can refer to when diagnosing and repairing products. Summary of the invention

[0006] Example embodiments are described herein. In a first aspect of the specification, a method performed by a vehicle repair tool is provided, comprising: at least one processor and a network interface, wherein the at least one processor is configured to diagnose a specific vehicle by checking a diagnostic problem code (DTC) set in the specific vehicle, and wherein the network interface is connected to the at least one processor and is operably connected to a wired communication link on the specific vehicle, the method comprising: receiving a set of search terms by the at least one processor, wherein the set of search terms includes a first term indicating at least a portion of a vehicle type identifier associated with the specific vehicle and a second term indicating a symptom exhibited by the specific vehicle; wirelessly sending a request for a repair reminder by the network interface to a communication network including a computing system outside the specific vehicle, wherein the request includes the set of search terms; in response to the request, sending a repair reminder by the network interface to a computing system outside the specific vehicle; a network interface wirelessly receiving the maintenance reminder from the computing system outside the particular vehicle via the communications network; and displaying the maintenance reminder through a user interface connected to the at least one processor, wherein the maintenance reminder includes a first phrase and a second phrase, wherein the first phrase describes a first process performed on a second vehicle exhibiting the symptom, wherein the first process performed on the second vehicle produces a result insufficient to determine that a component of the second vehicle associated with the symptom is defective, wherein the second phrase describes a second process performed on a given vehicle, the given vehicle being the second vehicle or a third vehicle also exhibiting the symptom, and wherein the second process performed on the given vehicle produces a result sufficient to determine that a component of the given vehicle associated with the symptom is defective, the component of the given vehicle being equivalent to the component of the second vehicle.

[0007] In a second aspect of the specification, a vehicle repair tool is provided, comprising: at least one processor; a network interface connected to the at least one processor and operably connected to a wired communication link on a specific vehicle; and a user interface connected to the at least one processor, wherein the at least one processor is configured to diagnose the specific vehicle by checking a diagnostic problem code (DTC) set in the specific vehicle, and receive a set of search terms, wherein the set of search terms includes a first term indicating at least a portion of a vehicle type identifier associated with the specific vehicle and a second term indicating a symptom exhibited by the specific vehicle, wherein the network interface is configured to wirelessly send a request for a repair reminder to a communication network including a computing system outside the specific vehicle, wherein the request includes the set of search terms, and wherein the network interface is configured to respond to the request. the request, wirelessly receiving the maintenance reminder from the computing system outside the particular vehicle via the communication network, and wherein the user interface is configured to display the maintenance reminder, wherein the maintenance reminder includes a first phrase and a second phrase, wherein the first phrase describes a first process performed on a second vehicle exhibiting the symptom, wherein the first process performed on the second vehicle produces a result insufficient to determine that a component of the second vehicle associated with the symptom is defective, wherein the second phrase describes a second process performed on a given vehicle, the given vehicle being the second vehicle or a third vehicle also exhibiting the symptom, and wherein the second process performed on the given vehicle produces a result sufficient to determine that the component of the given vehicle associated with the symptom is defective, the component of the given vehicle being equivalent to the component of the second vehicle.

[0008] In a third aspect of the specification, a non-transitory computer-readable medium is provided, which is configured to store at least computer-readable instructions, which, when executed by at least one processor of a vehicle service tool, cause the vehicle service tool to perform multiple functions, wherein the vehicle service tool is configured to diagnose a specific vehicle by checking a diagnostic problem code (DTC) set in the specific vehicle, wherein the vehicle service tool includes a network interface, which is connected to the at least one processor and is capable of being operably connected to a wired communication link on the specific vehicle, wherein the multiple functions include: receiving a set of search terms, wherein the set of search terms includes a first term indicating at least a portion of a vehicle type identifier associated with the specific vehicle and a second term indicating a symptom exhibited by the specific vehicle; wirelessly sending a request for a service reminder to a communication network including a computing system external to the specific vehicle, wherein the request for a service reminder is sent to a computing system external to the specific vehicle; wherein the request includes the set of search terms; in response to the request, wirelessly receiving the maintenance prompt from the computing system outside the particular vehicle via the communication network; and displaying the maintenance prompt through a user interface, wherein the maintenance prompt includes a first phrase and a second phrase, wherein the first phrase describes a first process performed on a second vehicle exhibiting the symptom, wherein the first process performed on the second vehicle produces a result that is insufficient to determine that a component of the second vehicle associated with the symptom is defective, and wherein the second phrase describes a second process performed on a given vehicle, the given vehicle being the second vehicle or a third vehicle that also exhibits the symptom and wherein the second process performed on the given vehicle produces a result that is sufficient to determine that the component of the given vehicle associated with the symptom is defective, the component of the given vehicle being equivalent to the component of the second vehicle.

[0009] These and other aspects and advantages will become apparent to those skilled in the art by reading the following detailed description with reference to the accompanying drawings where appropriate. In addition, it should be understood that the embodiments described in this summary and elsewhere are intended only as examples and do not necessarily limit the scope of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Example embodiments are described herein with reference to the following drawings.

[0011] Figure 1 is a block diagram of a networked computing system;

[0012] Figure 2 is a block diagram of a computing system;

[0013] Figure 3 is a block diagram of a computing system;

[0014] Figure 4 is a flowchart describing an example method;

[0015] Figure 5 A sample repair prompt is shown.

[0016] Figure 6 An example data table stored by a computing system is shown.

[0017] Figure 7 An example phrase template is shown.

[0018] Figure 8 Example phrases are shown.

[0019] Fig. 9 Additional example phrases are shown. DETAILED DESCRIPTION

[0020] I. Introduction

[0021] Traditionally, when diagnosing a symptom of a vehicle and servicing the vehicle to resolve the symptom, a maintenance technician may consult a maintenance manual in paper form or in electronic format stored on a computing device. In either case, the paper or electronic maintenance manual may become outdated over time, and the maintenance technician may not be aware of new technologies for servicing vehicles that other maintenance technicians have discovered. Therefore, it may be useful to be able to obtain the latest maintenance data submitted by many such maintenance technicians on a database shared among maintenance technicians. The database may be accessed via an electronic vehicle maintenance tool and / or other computing devices. It may also be useful to provide maintenance tips in the form of randomly changing phrase formats to better capture the attention of the maintenance technician who is viewing the maintenance tips.

[0022] For purposes of this specification, a vehicle is a mobile machine that can be used to transport a single person, multiple people, or cargo. As an example, any vehicle described herein can be driven or otherwise guided along a path (e.g., paved roads or otherwise) on land, in water, in the air, or in outer space. As another example, any vehicle described herein can be wheeled, tracked, railed, or gliding. As another example, any vehicle described herein can include an automobile, a motorcycle, an all-terrain vehicle (ATV) as defined by ANSI / SVIA-1-2007, a snowmobile, a personal watercraft (e.g., a JET As another example, any vehicle described herein may include or use any suitable voltage or current source, such as a battery, an alternator, a fuel cell, etc., to provide any suitable current or voltage, such as about 12 volts, about 42 volts, etc. As another example, any of the vehicles described herein may include or use any desired system or engine. These systems or engines may include items that use fossil fuels (e.g., gasoline, natural gas, propane, etc.), electricity (e.g., electricity generated by batteries, magnetos, fuel cells, solar cells, etc.), wind power, and hybrid power, or a combination thereof. As another example, any vehicle described herein may include an electronic control unit (ECU), a data link connector (DLC), and a vehicle communication link that connects the DLC to the ECU.

[0023] Although many of the example embodiments are described with respect to vehicles, the example embodiments may be applicable to products or serviceable items other than vehicles. As examples, other products or serviceable items may include household appliances, such as generators, refrigerators, dishwashers, or washing machines; or consumer electronic devices, such as televisions, cellular phones, or tablet devices. Other examples of other products or serviceable items are also possible. Therefore, for embodiments based on these other products or serviceable items, the term vehicle in the described embodiments may be replaced with the name of the other product or serviceable item.

[0024] In this specification, the article "one" or "an" is used to introduce the elements of the exemplary embodiments. Unless otherwise specified, or unless the context clearly stipulates otherwise, any reference to "one" or "an" refers to "at least one", and any reference to "the" refers to "the at least one". The intention of using these articles is to refer to one or more of these elements. The intention of using the conjunction "or" within a list of at least two terms described is to indicate any one of the listed terms or any combination of the listed terms. The use of ordinals such as "first", "second", "third", etc. is to distinguish the corresponding elements rather than to indicate a specific order of these elements. For the purpose of this specification, the terms "multiple" and "many" refer to "two or more" or "more than one".

[0025] The block diagram and flow chart shown in the accompanying drawings are provided only as examples and are not intended to be restrictive. Many of the elements shown in the accompanying drawings or described herein are functional elements, which can be implemented as discrete or distributed elements or combined with other elements and realized in any suitable combination and position. Those skilled in the art will recognize that other arrangements and elements (for example, machines, interfaces, functions, sequences or functional groups) can be used alternatively. In addition, the various functions described as being performed by one or more elements of the machine described herein can be realized by a processor performing a computer-readable program instruction or by any combination of hardware, firmware or software.

[0026] II. Sample Architecture

[0027] Figure 1 is a block diagram of a system 100 according to one or more example embodiments. Figure 1 Various combinations of the elements shown in can be arranged as other systems or subsystems to perform the example embodiments described herein. System 100 includes a computing system 102 (e.g., a vehicle maintenance data (VRD) system) and a network 104. Network 104 may include a wide area network (WAN), such as the Internet or a portion thereof. Additionally or alternatively, network 104 may include a wireless network, a wired network, a local area network (LAN), or some other type of network. Network 104 may include two or more of the aforementioned example networks.

[0028] System 100 includes computing systems 108, 110, 112, 116, 118, and 120. Computing systems 108-120 may take the form of a vehicle repair tool (VRT). Any of computing systems 108-120 described herein may, but are not required to, be configured to generate or send an original repair order (RO) to computing system 102. An operator of computing system 102 may use a RO manual input device (e.g., Figure 2 The RO manual input device 202 shown in FIG. 2 enters the original RO into the computing system 102. The manually entered RO can be stored in a data storage device, for example, Figure 2 The data storage device 210 is shown in FIG.

[0029] Computing systems 108-120 may represent vehicle maintenance tools configured to perform various functions. For example, any of computing systems 108-120 may send a request to computing system 102 for maintenance tips stored at and / or generated by computing system 102. The request may be sent using network 104. Any of computing systems 108-120 may also receive maintenance tips sent from computing system 102 using network 104 or otherwise provided or generated by computing system 102. Any of computing systems 108-120 may also present the received maintenance tips via a user interface.

[0030] Next, Figure 2 1 is a block diagram illustrating details of a computing system 102 (e.g., a vehicle repair data (VRD) system). The computing system 102 may include, be configured as, or be referred to as a server system, a server device, or more simply a server. According to embodiments in which the computing system 102 operates as a server, the computing system 102 may serve one or more computing systems 108-120 (e.g., a vehicle repair tool (VRT)) operating as a client device of the server.

[0031] The computing system 102 includes an RO manual input device 202 , a processor 204 , a user interface 206 , a network interface 208 , and a data storage device 210 , all of which may be linked together via a system bus, network, or other connection mechanism 212 .

[0032] The RO manual input device 202 may include one or more devices for inputting data displayed on a printed RO into the computing system 102 to be stored as an original RO within a maintenance order (RO) 214. As an example, the RO manual input device 202 may include a scanner device with or without an optical character recognition software application. As another example, the RO manual input device 202 may include a keyboard for entering (e.g., typing) data displayed on a printed RO and sending the entered (e.g., typed or otherwise entered) data to the processor 204 for storage as an original RO within the RO 214. As another example, the RO manual input device 202 may include a device that accepts a data storage device (e.g., a CD-ROM including data representing an original RO generated by a VRT). As another example, the RO manual input device 202 may include a laptop or desktop computing device having a display or connected to a display.

[0033] The original RO may be displayed by RO manual input device 202 or user interface 206. For any of a variety of reasons, such as security of information located in the original RO, computing system 102 may be configured so that the original RO generated by a first computing system (e.g., computing system 108) is not provided to a second computing system, such as computing system 116. In other examples, computing system 102 may generate a presentable RO based at least in part on information on the original RO generated by computing system 108, and provide the presentable RO to computing system 116.

[0034] A processor such as processor 204 may include one or more general purpose processors (e.g., an Intel single core microprocessor or an Intel multi-core microprocessor), or one or more special purpose processors (e.g., a digital signal processor). A processor such as processor 204 may be configured to execute computer readable program instructions, such as computer readable program instructions (CRPI) 218. For purposes of this specification, processor 204 executing CRPI 218 to perform certain functions described herein may include executing portions of CRPI 218 or the entirety of CRPI 218. Executing portions of CRPI 218 or the entirety of CRPI 218 may include executing some of the computer readable program instructions multiple times.

[0035] The user interface 206 may include interfaces to components operable to receive input, data, or information into the computing system 102, or to components that may present data or information output for the computing system 102. These components may be referred to as user interface components. The user interface 206 may include one or more audio / visual ports or communication ports connected to the user interface components via a wired or wireless user interface communication link.

[0036] User interface 206 may include one or more of the user interface components. As examples, the user interface components may include an infrared remote control device, a display device, a speaker configured to convert electrical signals into audible sounds, a keyboard, a touch screen, a pointing device such as a computer mouse, or some other component for generating signals to input data or information into computing system 102 or presenting data or information output by user interface 206.

[0037] User interface 206 may include a transmitter or transceiver for providing data or information to another user interface component or another element of computing system 102. The data or information provided by user interface 206 may include, but is not limited to, maintenance tips including maintenance tips 220.

[0038] The network interface 208 may include an interface to one or more communication networks (e.g., network 104). In order to be used in the case of a wireless communication network, the network interface 208 may include one or more antennas for sending or receiving wireless communications. The network interface 208 may include one or more communication ports configured to be connected to a wired communication link of the network, such as a coaxial cable, an Ethernet cable, a fiber optic cable, a digital subscriber line (DSL), a telephone line of a public switched telephone network (PSTN), or some other wired connectors. The network interface 208 may include a network controller, which includes a transmitter, a receiver, or a transceiver. A transmitter or a transceiver may provide data or information to a communication port to be transmitted through a connected network as a network communication. A receiver or a transceiver may receive data or information received at a communication port from a connected network.

[0039] A data storage device such as data storage device 210 may include a non-transitory computer-readable storage medium that is readable by processor 204. In an alternative arrangement, data storage device 210 may include two or more non-transitory computer-readable storage media. Each non-transitory computer-readable storage medium may include a volatile or non-volatile storage component, such as an optical, magnetic, organic or other memory or disk storage device, which may be integrated in whole or in part with a processor such as processor 204.

[0040] The data storage device 210 may store various data. The data stored by the data storage device 210 may be data provided to the data storage device 210 for storage from the RO manual input device 202, the processor 204, the user interface 206, or the network interface 208. Figure 2 As shown in FIG. 1 , the data storage device 210 may store a repair order (RO) 214, a classification term database 216, a computer readable program instruction (CRPI) 218, a repair reminder 220, metadata 222, vehicle utilization data 224, component utilization data 226, a text string 228, and a search term 230. The search term 230 may include, but is not limited to, a vehicle identification (i.e., vehicle ID) search term 232, such as a year / make / model / engine (Y / M / M / E) attribute and a symptom criteria 234.

[0041] RO 214 may include a computer-readable RO. The computer-readable RO may be arranged as a structured query language (SQL) file, an extensible markup language (XML) file, or some other type of computer-readable file or data structure. The RO within RO 214 may be received from RO manual input device 202, from network interface 208 via network 104, or from another device. The RO within RO 214 may be an original RO, for example, generated by Figure 1, or an RO entered using RO manual input device 202 , or a presentable RO generated by computing system 102 .

[0042] The mapping, standard, context item, or labor operation code may be stored as part of the classification item database 216. The classification item database 216 may include data identifying words or phrases that are associated with each other. The association may be based on words or phrases having a common meaning. Words or phrases identified as being associated with each other may be referred to as a "classification database group," or more simply, a "classification group."

[0043] The classification term database 216 may include one or more classification groups, and each classification group may include one or more classification terms (e.g., words or phrases). As an example, the classification term database 216 may include data identifying the following phrases as classification groups: (i) stall in cold, (ii) engine stops running when temperature is low, (iii) engine stalls in the morning, (iv) stalls in the morning, (v) stalls in the AM, and (vi) engine stalls in cold mornings.

[0044] Each classification group can be associated with a standard term, which can be the first word or first phrase added to the classification group. Alternatively, the word or phrase subsequently added to the classification group can be the standard term of the classification group. The word or phrase different from the standard term in the classification group can be a mapping term. The word or phrase in each classification group can be obtained from the RO. The administrator can approve the addition or modification of any classification group by, for example, the processor 204 that performs CRPI 218. The term in the classification term database 216 can be compared with the term on the computer-readable RO. The mapping term found on the original RO and in the given classification group can be represented on the presentable RO by the standard term of the given classification group.

[0045] The processor 204 may search for text, symbols or other content on the ROs of RO 214 or metadata associated with the ROs to associate ROs within a cluster of ROs (or more simply, a RO cluster). Each cluster of ROs may be associated with a defined RO attribute, such as a diagnostic problem code (DTC), action, or component listed on the RO. Other attributes of the information recorded on the RO may be associated with the RO cluster. Table 1 shows data for twenty-five clusters identified with IDs 1 to 25 (inclusive). The cluster size indicates how many ROs are associated with the corresponding cluster. The cluster size may be modified when or after additional ROs are added to RO 214. Table 1 shows examples of DTC, action, and component attributes associated with each corresponding RO cluster.

[0046]

[0047]

[0048] Table 1

[0049] Table 1 may be modified to also include separate columns for other attributes. The other attributes may identify RO attributes such as, but not limited to, customer complaints, dates, or labor operation codes (LOCs). As an example, customer complaints may include, but are not limited to, items such as rattling, not starting, and vibrations. Maintenance tips for these example customer complaint items may include maintenance tips that respectively identify methods to stop a vehicle from rattling, methods to repair a vehicle that will not start, and methods to stop a vehicle from vibrating.

[0050] Table 2 below shows an example of data included for 25 of the 2088 ROs associated with RO cluster ID 18 shown in Table 1. The RO data in Table 2 includes RO identifiers that may be assigned, for example, by the VRT or computing system 102. The RO data in Table 2 also includes year / make / model / engine attributes associated with each RO.

[0051]

[0052]

[0053] Table 2

[0054] Some vehicle models are associated with sub-model attributes. Some vehicle models are not associated with sub-model attributes. Table 2 can be modified to include a separate column for including sub-model attributes of vehicles associated with sub-model attributes. As an example, ROID 7923 is related to the Ford pickup F150 brand and model. The item "F150" can be called a sub-model attribute. Other sub-model attributes of the Ford pickup model may include "F250" and "F350" sub-model attributes. Sub-model attributes can be included on the RO. Searching for ROs or maintenance tips based on sub-models other than Y / M / M / E attributes can result in search results having ROs or maintenance tips associated with a specific sub-model, but there will be no other sub-models of a specific vehicle with a specific Y / M / M / E attribute. The "S" in Y / M / M / S / E can represent a sub-model attribute.

[0055] Table 2 may be modified to also include separate columns for other attributes. Other attributes may identify system (Sys) attributes, such as but not limited to transmission attributes, suspension attributes, and audio system attributes. The attribute set including system attributes may be referred to as Y / M / M / E / Sys attributes.

[0056] The vehicle utilization data 224 may include computer readable data identifying different vehicle models built on a common vehicle platform. Vehicles built on a common platform may have many similarities, including the use of common components or part numbers. Vehicles built on a common platform may experience similar vehicle symptoms due to similar causes, such as failure of components common to vehicles built on the common vehicle platform. Table 3 shows an example of data that may be stored as the vehicle utilization data 224.

[0057] Processor 204 may generate RO clusters covering multiple vehicle models, for example, the three vehicle models of VLD-3 shown in Table 3. If RO 214 includes 100 ROs for Chevrolet Lumina APV models from 1990-1996 and a given repair condition, 150 ROs for Pontiac Tran Sport models from 1990-1996 and a given problem, and 40 ROs for Oldsmobile Silhouette models from 1990-1996 and a given problem, processor 204 may generate three separate RO clusters for 290 ROs, or a single RO cluster for 290 ROs. A larger amount of ROs may indicate a greater likelihood of a successful repair for a given problem.

[0058]

[0059] Table 3

[0060] The processor 204 may use the exception data within the vehicle utilization data 224 to exclude ROs associated with certain vehicle models from the RO clusters associated with a group of vehicles built on a common platform. For the exception data in Table 3, since the GMC Yukon uses a different radiator than the Cadillac Escalade, Chevrolet Tahoe, and Chevrolet Suburban, the RO cluster associated with the radiator of the GMC Yukon may not be grouped together with the RO cluster associated with the radiator of the Cadillac Escalade, Chevrolet Tahoe, and Chevrolet Suburban.

[0061] Part utilization data 226 may include data identifying different vehicle models that use common parts produced by one or more part manufacturers. For purposes of this specification, a common part is a part that can be used in any one of two or more vehicle models without changing the part or any of the two or more vehicles to use the common part. Various references to common parts, for example, part numbers or part names used by any or all of one or more part manufacturers for different vehicle models may be used. Vehicle models using common components may experience similar vehicle symptoms due to similar causes, for example, common part failures. Table 4 shows an example of data that may be stored as part utilization data 226.

[0062]

[0063]

[0064] Table 4

[0065] Processor 204 may generate RO clusters covering common vehicle components and multiple vehicle models, for example, the coolant temperature sensor of PLD-1 and three vehicle models shown in Table 4. If RO 214 includes 30 ROs for a 2012 Cadillac Escalade model and a coolant temperature sensor, 40 ROs for a 2012 Chevrolet Tahoe model and a coolant temperature sensor, and 20 ROs for a 2012 Chevrolet Suburban model and a coolant temperature sensor, processor 204 may generate three separate RO clusters for the 90 ROs, or a single RO cluster for the 90 ROs. A greater number of ROs may indicate a greater likelihood that a successful repair will occur for a given problem caused by the coolant temperature sensor.

[0066] CRPI 218 may include program instructions executable by processor 204 to implement functions described herein or executable by computing system 102. CRPI 218 may include program instructions executable to parse data from an original RO stored in RO 214 and identify service process information, vehicle identification, and component usage information from the original RO for use in generating a renderable RO or for increasing a count of a cluster size if a renderable RO related to the original RO has already been generated.

[0067] CRPI 218 may include program instructions executable by processor 204 to generate metadata associated with at least one set of search terms for each maintenance reminder and based on the RO stored in RO 214. Metadata 222 may include metadata generated by processor 204 based on information listed on the original RO, including, but not limited to, the LOC and the definition of the LOC.

[0068] The CRPI 218 may include program instructions executable by the processor 204 to determine that a word or phrase within the service process information (e.g., service process information) is within one or more classification groups of the classification term database 216, and to associate (e.g., link) the service process information with the one or more classification groups. The service process information associated with any given classification group may be part of a new RO cluster or additional service process information to be added to the RO cluster or to modify the RO cluster.

[0069] The text string 228 (e.g., a phrase template or phrase) may include a text string (e.g., two or more words, numbers, or symbols). The text string may include one or more gaps for inserting metadata to complete the text string. The text string may include a complete text string without any gaps. The processor 204 may select one or more text strings to be associated with a set of terms (e.g., search terms) that may be input or received to search for maintenance tips for the maintenance tips 220. The processor 204 may select metadata to be inserted into the gaps in the text string. The text string 228 may include a text string representing an input received by the user interface 206. The text string 228 may include a text string received by the network interface 208.

[0070] The search terms 230 may include various sets of search terms. The sets of search terms may include a vehicle ID search term 232 or a symptom criteria 234. A first example set of search terms may include search terms received by the network interface 208 as part of a request for a maintenance tip. The first example set of search terms may include search terms that are non-standard terms in the classification term database 216 and may be referred to as non-standard search terms (NSST). The processor 204 may identify standard terms within the classification term database 216 that match the search terms received by the network interface 208 and then use any standard terms included within the received search terms or identified from the classification term database 216 to search for maintenance tips. The non-standard search terms stored as part of the search terms 230 may then be viewed by the processor 204 or a person using the RO manual input device 202 or the user interface 206 to include as part of the classification term database 216.

[0071] The second example set of search terms may include a standard set of search terms and may be referred to as standard search terms (SST). The standard set of search terms may include standard vehicle ID search terms (e.g., Y / M / M / E attributes) defined in the classification term database 216 and standard symptom criteria defined in the classification term database 216. The processor 204 may associate one or more standard sets of search terms with a repair reminder or repair order. The set of search terms associated with a repair reminder or repair order may be stored as metadata associated with the repair reminder or repair order. The classification term database 216 may include search terms 230. The second example set of search terms may be associated with more than one set of search terms, such as the first example set of search terms.

[0072] Table 5 shows an example of search terms that may be stored in search terms 230. NSST-227 is associated with SST-15. SST-15 is associated with RO ID 3915. In response to receiving NSST-227, determining that SST-15 is associated with NSST-227, and determining that RO ID 3915 is associated with SST-15, a maintenance reminder corresponding to RO ID 3915 may be identified. SST-1456 is a set of standard search terms having symptom criteria common to SST-15 and SST-1456, and a Y / M / M / E attribute that differs from the Y / M / M / E of SST-15 only by the model year (i.e., 2000 instead of 1999). Both SST-15 and SST-1456 are associated with RO ID 3915. The association may be determined based on vehicle utilization data 224 or component utilization data 226.

[0073]

[0074] Table 5

[0075] The vehicle ID search term 232 is an example of a search term that may be included within the search term 230. The vehicle ID search term 232 may include various optional attributes. For example, the attributes of the vehicle ID search term 232 may include the Y / M / M / E attributes. As another example, the attributes of the vehicle ID search term 232 may include the year / make / model / sub-model / engine (Y / M / M / S / E) attributes discussed with respect to Table 2. As another example, the attributes of the vehicle ID search term 232 may include the year / make / model / engine / system (Y / M / M / E / Sys) attributes. As another example, the attributes of the vehicle ID search term 232 may include the year / make / model / sub-model / engine / system (Y / M / M / S / E / Sys) attributes.

[0076] The system (Sys) attribute vehicle ID search term 232 may indicate or represent a system (e.g., one or more systems) or a component (e.g., one or more components) within a vehicle. As examples, the system or component within a vehicle may identify (i) a powertrain transmission within a vehicle (e.g., a 4-speed automatic transmission with overdrive), (ii) a rear differential within a vehicle (e.g., a rear differential with a 4.11:1 gear ratio), (iii) an electric alternator within a vehicle (e.g., a 100-amp alternator), (iv) a heating, ventilation, and air conditioning (HVAC) system installed within the vehicle (e.g., a dual-zone (e.g., driver-side and passenger-side) HVAC system), or some other system or component installed within, attached to, or otherwise operating on or in a vehicle.

[0077] The order of any of the vehicle ID search terms 232 described herein can be rearranged as desired. For example, the order of the Y / M / M / E attributes can be rearranged to the Make / Model / Engine / Year (M / M / E / Y) attributes or arranged in another manner.

[0078] Next, Figure 3 1 is a block diagram showing details of an example computing system 108, such as a vehicle repair tool (VRT). The computing system 108 includes a user interface 302, a processor 304, a network interface 306, and a data storage device 308, all of which may be linked together via a system bus, network, or other connection mechanism 310. Figure 1 One or more of the computing systems 108 - 120 shown in can be arranged as computing system 108 , and vice versa.

[0079] Processor 304 may be configured to execute computer-readable program instructions stored within data storage device 308, such as computer-readable program instructions (CRPI) 312. For purposes of this description, processor 304 executing CRPI 312 to perform a function described herein may include executing a portion of CRPI 312 or the entirety of CRPI 312. Executing a portion of CRPI 312 or the entirety of CRPI 312 may include executing some of the computer-readable program instructions multiple times.

[0080] The data storage device 308 may include a non-transitory computer-readable storage medium (i.e., two or more computer-readable storage media) that may be read by the processor 304. The non-transitory computer-readable storage medium (or each) may include a volatile or non-volatile storage component, such as an optical, magnetic, organic or other memory or disk storage device, which may be integrated with the processor 304 in whole or in part.

[0081] The user interface 302 may include an interface for a component configured to receive input for a computing system 108, or an interface for a component configured to present data or information output for a computing system 108. Any of these components may be referred to as a VRT user interface component. The user interface 302 may include one or more audio / visual ports or communication ports connected to the VRT user interface component via a wired or wireless user interface communication link. The data, input or information received by the computing system 108 via the user interface 302 may include data or information for preparing an RO.

[0082] The user interface 302 may include one or more of the VRT user interface components. As examples, the VRT user interface components may include an infrared remote control device, a display device, a speaker configured to convert electrical signals into audible sounds, a keyboard, a touch screen, a pointing device such as a computer mouse, or some other component for generating signals to input data or information into the computing system 108 or present data or information output by the user interface 302. The user interface 302 may include a transmitter or transceiver for providing data or information to another VRT user interface component.

[0083] The network interface 306 may include an interface to one or more communication networks (e.g., network 104). In order to be used in the case of a wireless communication network, the network interface 306 may include one or more antennas for sending or receiving wireless communications. The network interface 306 may include one or more communication ports configured to be connected to a wired communication link of the network. Examples of wired communication links are listed elsewhere in this article. The network interface 306 may include a network controller, which includes a transmitter, a receiver, or a transceiver. The transmitter or transceiver may provide data or information to the communication port to be transmitted through the connected network as a network communication. The receiver or transceiver may receive data or information received at the communication port from the connected network. The data or information provided to the network by the network interface 306 may include an RO.

[0084] The CRPI 312 may include program instructions for generating an RO based on input received by the user interface 302 or a user interface component thereof. The CRPI 312 may include program instructions for performing diagnostic functions for diagnosing the vehicle identified on the RO. As an example, performing the diagnostic function may include checking for diagnostic problem codes (DTCs). The CRPI 312 may include program instructions for: (i) displaying, by the user interface 302, vehicle ID attributes that may be selected to form a search term set, symptom criteria that may be selected to form part of the search term set, and fields for entering a usage indicator (e.g., vehicle mileage or engine hours), (ii) receiving a selection of the search term set, (iii) providing the selected search term set to the network interface 306 to transmit the selected search term to the computing system 102, (iv) receiving a maintenance reminder from the computing system 102 via the network interface 306, and (v) displaying the received maintenance reminder using the user interface 302.

[0085] III. Sample Operation

[0086] Figure 4 400. The method 400 includes the functions shown in blocks 402 and 404. Various methods may be performed using one or more of the functions shown in the method 400 and one or more other functions described herein. Figure 4 Reference numerals within the description are provided as examples and do not limit the description to only the specific configuration including the components associated with the reference numerals.

[0087] Method 400 may be performed by a first computing system, such as computing system 102. Block 402 includes receiving a message from a second computing system that identifies a symptom of a first vehicle. For example, computing system 102 may receive a message from computing system 108 indicating that a check engine light of the first vehicle is on. The message may be received via network 104. Other symptoms are also possible, such as, the engine of the first vehicle does not start, the brake lights of the first vehicle are off, and so on. The message may indicate the make, model, sub-model, trim package, and / or year of manufacture of the first vehicle. For example, the message may indicate that the first vehicle is a 2002 Toyota Celica GT. The first vehicle may belong to a customer of a repair shop where the customer took the first vehicle to be repaired. Computing system 108 may receive input entered by a repair technician who is working on the first vehicle. The received input may represent information about the first vehicle included in the message sent by computing system 108 to computing system 102.

[0088] Block 404 includes sending the maintenance reminder to a second computing system. For example, computing system 102 may Figure 5 The maintenance reminder 500 is sent in the form of data to the computing system 108 (i.e., the computing system from which the computing system 102 receives the message including information about the first vehicle and the symptoms of the first vehicle). The maintenance reminder 500 may be sent via the network 104. Figure 5 As shown in , the computing system 108 can then display the maintenance reminder for viewing by a maintenance technician or another user.

[0089] Maintenance reminder 500 may include title phrase 502, complaint phrase 504, reason phrases 506, 508, 512, 514, and 516, and correction phrase 518. Phrases 502-518 may be selected or generated by computing system 102 based on information included in a message received by computing system 102 from computing system 108.

[0090] The title phrase 502 may include a brief summary of one or more diagnostic or corrective procedures performed on components of the additional vehicle. (In the context of describing the maintenance reminder 500 herein, the "additional vehicle" may in some cases be at least two additional vehicles. That is, the maintenance reminder 500 may include information related to multiple vehicles that are similar to the first vehicle and on which similar diagnostic or corrective procedures have been performed with similar results.) The title phrase 502 includes "P0335, Replace crankshaft position sensor."

[0091] Complaint phrases 504 may describe symptoms of the additional vehicle that indicate a potential problem or malfunction associated with a component of the additional vehicle. Complaint phrases 504 include "The customer states that the check engine light is on."

[0092] The reason phrases 506-516 may describe the corresponding diagnostic procedures performed on the component of the additional vehicle. The maintenance prompt 500 generally includes at least one "non-condemning" reason phrase, i.e., a phrase describing a procedure performed on the additional vehicle that produced a result insufficient to determine that the component of the additional vehicle associated with the symptom is defective. In some examples, performing the procedure suggested by the non-condemning phrase may help the maintenance technician working on the first vehicle find a "simple fix" for the symptom, such as reconnecting a wire or cleaning a corroded contact. The maintenance prompt 500 generally also includes at least one "condemning" reason phrase, i.e., a phrase describing a procedure performed on the additional vehicle that produced a result sufficient to determine that the component of the additional vehicle associated with the symptom is defective. In some examples, the procedure suggested by the condemning phrase may be more time-consuming, more expensive, or more cumbersome than the procedure suggested by the non-condemning phrase, but sometimes it may be necessary to perform such a procedure so that the component can be properly diagnosed or the fault can be corrected. Phrases 506, 508, 512, and 514 are examples of non-condemning phrases, while phrase 516 is an example of a condemning phrase.

[0093] (Non-blaming) Phrase 506 includes "Connected the scan tool and found the P0335 crankshaft position sensor 'A' circuit." (Non-blaming) Phrase 508 includes "Using the scan tool, monitored the engine speed parameters and found the parameters to drop out intermittently." (Non-blaming) Phrase 512 includes "Performed a visual inspection of the crankshaft position sensor and found no faults." (Non-blaming) Phrase 514 includes "Using a lab oscilloscope, measured power and ground at the crankshaft position sensor and found both power and ground to be present." (Non-blaming) Phrase 516 includes "Using a lab oscilloscope, monitored the crankshaft position sensor signal and found the signal to drop out intermittently."

[0094] In other examples, the maintenance reminder 500 may include more or fewer phrases. The reason words 506-516 describe corresponding procedures performed on additional vehicles that display the same symptom as the first vehicle (e.g., the check engine light is on). The computing system 102 may store data related to the corresponding procedures that have been performed (e.g., in a maintenance order or maintenance record). In one example, such data (e.g., data submitted by a different maintenance technician) may be sent from the third computing system 110 to the computing system 102. It should be understood herein that in some examples, any of the phrases 506-516 may describe corresponding procedures performed on a separate vehicle or on the same vehicle.

[0095] (Non-condemning) phrase 506 describes a first process performed on an additional vehicle. In this case, the first process performed on the additional vehicle produces results insufficient to determine that a component of the additional vehicle associated with the symptom is defective. As indicated by phrase 506, the first process may include connecting a scan tool to a crankshaft position sensor circuit and causing the scan tool to return a diagnostic error code P0335. As described below, the additional vehicle may be associated with the first vehicle in a variety of ways. Therefore, information about the additional vehicle may be useful for repairing the first vehicle.

[0096] (Non-condemning) phrase 508 describes a second process performed on an additional vehicle. In this case, the results produced by the second process performed on the additional vehicle are insufficient to determine that a component of the additional vehicle associated with the symptom is defective. As indicated by phrase 508, the second process may include using a scan tool to monitor an engine speed parameter of the additional vehicle and finding that the engine speed parameter is intermittently dropped out. Using the scan tool to find that the engine speed parameter is intermittently dropped out may not be sufficient to determine whether the crankshaft position sensor of the additional vehicle is defective.

[0097] (Non-condemning) phrase 512 describes a third process performed on an additional vehicle. In this case, the results produced by the third process performed on the additional vehicle are insufficient to determine that the component of the additional vehicle associated with the symptom is defective. As indicated by phrase 512, the third process may include performing a visual inspection of the crankshaft position sensor and finding no fault. Performing a visual inspection of the crankshaft position sensor and finding no fault may not be sufficient to determine whether the crankshaft position sensor of the additional vehicle is defective.

[0098] (Non-condemning) phrase 514 describes a fourth process performed on an additional vehicle. In this case, the fourth process performed on the additional vehicle produces results insufficient to determine that a component of the additional vehicle associated with the symptom is defective. As indicated by phrase 514, the fourth process may include using a laboratory oscilloscope to measure power and ground at the crankshaft position sensor and finding that both power and ground are present. Using a laboratory oscilloscope to measure power and ground at the crankshaft position sensor and finding that both power and ground are present may not be sufficient to determine that the crankshaft position sensor of the additional vehicle is defective.

[0099] (Condemned) Phrase 516 describes a fifth process performed on the additional vehicle. Compared to the first, second, third, and fourth processes described by corresponding phrases 506, 508, 512, and 514, the fifth process performed on the additional vehicle produces results sufficient to determine that the component of the additional vehicle associated with the symptom is defective. As shown in phrase 516, the fifth process can include using a laboratory oscilloscope to monitor the crankshaft position sensor signal and learning that the crankshaft position sensor signal intermittently drops out. Using a laboratory oscilloscope to monitor the crankshaft position sensor signal and finding that the crankshaft position sensor signal intermittently drops out can be sufficient to determine that the crankshaft position sensor of the additional vehicle is defective.

[0100] Correction phrase 518 describes the correction process performed with respect to the component of the additional vehicle. For example, phrase 518 includes "The crankshaft position sensor was replaced, the code was cleared, and a road test of the vehicle was performed. The customer's concerns did not recur."

[0101] The maintenance reminder 500 is shown as including eight phrases, but in other examples, the maintenance reminder may include any number of phrases.Such maintenance reminders generally include at least one non-reprimanding phrase and at least one reprimanding phrase.

[0102] The method 400 may also involve generating the maintenance reminder 500 by generating one or more of the phrases 502-518. In this case, sending the maintenance reminder to the second computing system may include sending the generated phrases 502-518 to the second computing system.

[0103] For example, computing system 102 may generate maintenance reminder 500 using various data stored at data storage device 210 and the content of a message received from computing system 108. For example, a message received by computing system 102 from computing system 108 may indicate that the first vehicle is a 2002 Toyota Celica GT and that the check engine light of the first vehicle is on. In response, computing system 102 may search data storage device 210 for data corresponding to other vehicles associated with the first vehicle and that have displayed a check engine light that is on. For example, computing system 102 may search for records corresponding to a 2000-2005 model Toyota Celica GT or GTS trim package that displays a check engine light that is on. Computing system 102 may also search for data related to the first vehicle in other ways. For example, computing system 102 may search for data related to vehicles that are different in make, model, and / or year but are known to share common components. Computing system 102 may use such data to generate a maintenance reminder including phrases 502-518 to send to computing system 108.

[0104] For example, computing system 102 may identify data stored at data storage device 210. Based on the content of the message received by computing system 102 from computing system 108, computing system 102 may at least identify Figure 6 The maintenance record groups 608, 612, 614, 616, and 620 of the data table 600 contain related data. That is, the maintenance record groups 608-620 may each correspond to a vehicle manufactured between 2000-2005, which are Toyota Celica GT or Toyota Celica GTS, and indicate that the check engine light is on.

[0105] By way of further example, computing system 102 may store at data storage device 210 Figure 7 708, 712, 714, 716, 720, and 722. Computing system 102 may (e.g., randomly) select phrase template 708 to insert data 609, 611, and 613. Computing system 102 may (e.g., randomly) select phrase template 712 to insert data 615, 617, and 619. Computing system 102 may (e.g., randomly) select phrase template 714 to insert data 621, 623, and 625. Computing system 102 may (e.g., randomly) select phrase template 716 to insert data 627, 629, and 631. In other examples, any of phrase templates 708-722 may be assigned to different identified data, or may be selected from the plurality of phrase templates 708-722. Figure 7 Phrase templates not shown in the figure are assigned to various other data.

[0106] Phrase templates 708-722 may be reason phrase templates. Reason phrase templates may be used to generate reason phrases, i.e., phrases that describe the diagnostic process performed on a vehicle component. Data from the fields "Associated Component", "Tool or Technique Used", "Diagnostic Action Performed", and / or "Result of Diagnostic Action" of data table 600 may be inserted into the reason phrase templates to generate a blame or non-blame reason phrase.

[0107] Computing system 102 may generate phrase 508 by inserting data 609, 611, and 613 into phrase template 708 at data fields 709, 711, and 713, respectively. Computing system 102 may generate phrase 512 by inserting data 615, 617, and 619 into phrase template 712 at data fields 715, 717, and 719, respectively. When computing system 102 is generating phrase 512, computing system 102 may determine that data 615 and 617 have redundant data "visual inspection." Therefore, computing system 102 may remove the redundant narration of "visual inspection" from phrase 512. Computing system 102 may generate phrase 514 by inserting data 621, 623, and 625 into phrase template 714 at 721, 723, and 725, respectively. Computing system 102 may generate phrase 516 by inserting data 627 , 629 , and 631 into phrase template 716 at 727 , 729 , and 731 , respectively.

[0108] In some examples, the computing system 102 may non-randomly select a phrase template for inclusion in the maintenance prompt 500. For example, the computing system 102 may determine that the phrase template 708 is the least recently selected phrase template of any of the phrase templates 708-722 stored by the computing system 102. In response, the computing system 102 may select the phrase template 708 based on the determination. Any of the phrase templates 712-722 selected for the maintenance prompt 500 may be selected in any of the manners described herein.

[0109] In some examples, identifying data to be included in the phrase template may include determining that such data corresponds to a data field of the phrase template. Accordingly, inserting such data into the phrase template may include inserting the data into a corresponding data field of the phrase template.

[0110] For example, computing system 102 may store data indicating that data fields 709, 711, and 713 correspond to data fields "tool or technique used," "diagnostic action performed," and "result of diagnostic action," respectively, of data table 600. Therefore, computing system 102 may determine that data 609, 611, and 613 correspond to data fields 709, 711, and 713, respectively, of phrase template 708. After determining that data 609, 611, and 613 correspond to data fields 709, 711, and 713, respectively, computing system 102 may insert data 609, 611, and 613 into data fields 709, 711, and 713, respectively, thereby generating phrase 708.

[0111] Computing system 102 may also store data indicating that data fields 715, 721, and 727 correspond to the "tool or technique used" data field of data table 600, data fields 717, 723, and 729 correspond to the "diagnostic action performed" data field of data table 600, and data fields 719, 725, and 731 correspond to the "result of diagnostic action" data field of data table 600. Therefore, computing system 102 may determine that data 615, 617, and 619 correspond to data fields 715, 717, and 719, respectively, of phrase template 712. Computing system 102 may also determine that data 621, 623, and 625 correspond to data fields 721, 723, and 725, respectively, of phrase template 714. Computing system 102 may also determine that data 627, 629, and 631 correspond to data fields 727, 729, and 731, respectively, of phrase template 716.

[0112] 1, 723, and 725, respectively, thereby generating phrase 514. Computing system 102 may also enter data 627, 629, and 631 into data fields 727, 729, and 731, respectively, thereby generating phrase 516. Computing system 102 may also enter data 615, 617, and 619 into data fields 715, 717, and 719, respectively, thereby generating phrase 512. Computing system 102 may also enter data 621, 623, and 625 into data fields 721, 723, and 725, respectively, thereby generating phrase 514. Computing system 102 may also enter data 627, 629, and 631 into data fields 727, 729, and 731, respectively, thereby generating phrase 516.

[0113] Headline phrase 502 may similarly be generated by selecting a headline phrase template from the group of headline phrase templates stored in data storage device 210. An example headline phrase template may be ", Replace."; data from data fields "Diagnostic Trouble Code (DTC)" (not shown) and "Associated Component" of data table 600 may be inserted into the headline phrase template to generate headline phrase 502. The headline phrase template used to generate headline phrase 502 may be randomly selected from the group of headline phrase templates, or the headline phrase template may be selected based on a determination that the headline phrase template is the least recently selected headline phrase template in the group. Other examples are possible.

[0114] Complaint phrase 504 may similarly be generated by selecting a complaint phrase template from the set of complaint phrase templates stored in data storage device 210. An example title phrase template may be "Customer Notes." Data from data field "Symptoms" of data table 600 may be inserted into the complaint phrase template to generate complaint phrase 504. The template used to generate complaint phrase 504 may be randomly selected from the set of complaint phrase templates, or the complaint phrase template may be selected based on a determination that the complaint phrase template is the least recently selected complaint phrase template in the set. Other examples are possible.

[0115] The non-blame reason phrase 506 may be generated similarly to any of the reason phrases 508 - 516 discussed herein.

[0116] Correction phrase 518 may similarly be generated by selecting a correction phrase template from the group of correction phrase templates stored in data storage device 210. An example correction phrase template may be "Replaced, cleared the code, and performed a road test of the vehicle. The customer's concerns did not recur." Data from the data field "Associated Components" of data table 600 may be inserted into the correction phrase template to generate correction phrase 518. The correction phrase template may be randomly selected from the group of correction phrase templates, or the correction phrase template may be selected based on a determination that the correction phrase template is the least recently selected correction phrase template in the group. Other examples are possible.

[0117] Method 400 may also involve determining that neither the first process nor the second process is a visual inspection process. For example, computing system 102 may determine that the process described by phrase 508 is not a visual inspection process by reviewing data 609, 611, or 613 and determining that the process described by phrase 508 is instead a process involving a scanning tool. Similarly, computing system 102 may determine that the processes described by phrases 514 and 516, respectively, are not visual inspection processes by reviewing data 621, 623, 625, 627, 629, and / or 631 and determining that the processes described by phrases 514 and 516, respectively, are processes involving a laboratory oscilloscope.

[0118] Method 400 may also involve identifying, based on determining that neither the first process nor the second process is a visual inspection process, the following: (i) additional data stored by the first computing system, (ii) additional data associated with symptoms and components of the first vehicle, and (iii) additional data associated with the visual inspection process.

[0119] For example, computing system 102 may identify data 615, 617, and / or 619 of maintenance record group 612 corresponding to a visual inspection process. As shown, data 615, 617, and 619 are associated with a "check engine light" symptom. For example, as described above, phrase 512 may be generated by inserting data 615, 617, and 619 into phrase template 712. In this manner, in some examples, computing device 102 may ensure that maintenance prompt 500 includes at least one phrase describing the visual inspection process. In such an example, the maintenance prompt may include phrases 512 and 516, but not other reason phrases. In this case, computing system 102 may be configured to generate or select a maintenance prompt that includes (i) a condemnation phrase; and (ii) a non-condemnation phrase describing the visual inspection process.

[0120] Method 400 may also involve identifying data stored by computing system 102 that is associated with: (i) a make, model, or year of manufacture of an additional vehicle; (ii) symptoms of the additional vehicle; and (iii) a first procedure performed on the additional vehicle, and determining that the identified data corresponds to at least a predetermined amount (e.g., a threshold amount) of maintenance records stored by computing system 102.

[0121] In one example, the predetermined number of maintenance records may be 1200. Figure 6 , the computing system 102 may determine that the maintenance record group 608 includes 1000 maintenance records, the maintenance record group 612 includes 1500 maintenance records, the maintenance record group 614 includes 1250 maintenance records, and the maintenance record group 616 includes 1500 maintenance records. Therefore, in some examples, the computing system 102 may include the phrases 512, 514, and 516 in the maintenance prompt 500, but may exclude the phrase 508 from the maintenance prompt 500. In some instances, a threshold comparison may occur before generating the phrases, such that the phrase 508 is not generated because the maintenance record group 608 has less than a threshold number of maintenance orders.

[0122] exist Figure 8 and Fig. 9 In the example described in , computing system 102 may store phrases 508 and 528 constituting a first plurality of phrases, phrases 512 and 532 constituting a second plurality of phrases, phrases 514 and 534 constituting a third plurality of phrases, and phrases 516 and 536 constituting a fourth plurality of phrases. Phrases 508-516 and 528-536 may all be associated with a symptom of the first vehicle (e.g., the check engine light is on). Computing system 102 may store other phrases (not shown) that are not associated with a symptom of the first vehicle and / or that are associated with other symptoms.

[0123] As shown, phrase 508 may convey information equivalent to information conveyed by phrase 528, while phrase 508 may include different syntax and / or word selection than phrase 528. Phrase 512 may convey information equivalent to information conveyed by phrase 532, while phrase 512 may include different syntax and / or word selection than phrase 532. Phrase 514 may convey information equivalent to information conveyed by phrase 534, while phrase 514 may include different syntax and / or word selection than phrase 534. Phrase 516 may convey information equivalent to information conveyed by phrase 536, while phrase 516 may include different syntax and / or word selection than phrase 536.

[0124] Based on data table 600, computing system 102 may associate data 609, 611, and 613 for phrases 508 and 528 with maintenance record group 608. Thus, computing system 102 may identify phrases 508 and 528 as being associated with the first vehicle and the symptoms of the first vehicle based on the contents of data fields “make,” “model,” “year,” and “symptoms” of maintenance record group 608. Computing system 102 may associate data 615, 617, and 619 for phrases 512 and 532 with maintenance record group 612. Therefore, computing system 102 may identify phrases 512 and 532 as being associated with the first vehicle and the symptoms of the first vehicle based on the contents of the data fields “make,” “model,” “year,” and “symptoms” of maintenance record group 612. Computing system 102 may associate data 621, 623, and 625 of phrases 514 and 534 with maintenance record group 614. Therefore, computing system 102 may identify phrases 514 and 534 as being associated with the first vehicle and the symptoms of the first vehicle based on the contents of the data fields “make,” “model,” “year,” and “symptoms” of maintenance record group 614. Computing system 102 may associate data 627, 629, and 631 of phrases 516 and 536 with maintenance record group 616. Therefore, computing system 102 may identify phrases 516 and 536 as being associated with the first vehicle and the symptoms of the first vehicle based on the contents of the data fields “make,” “model,” “year,” and “symptoms” of maintenance record group 616.

[0125] By way of further example, computing system 102 may randomly or non-randomly select phrase 508 instead of phrase 528 for use in maintenance prompt 500. In other examples, computing system 102 may select phrase 528 instead of phrase 508. Similarly, computing system 102 may randomly or non-randomly select phrase 512 instead of phrase 532 for use in maintenance prompt 500. In other examples, computing system 102 may select phrase 532 instead of phrase 512. Additionally, computing system 102 may randomly or non-randomly select phrase 514 instead of phrase 534 for use in maintenance prompt 500. In other examples, computing system 102 may select phrase 534 instead of phrase 514. Additionally, computing system 102 may randomly or non-randomly select phrase 516 instead of phrase 536 for use in maintenance prompt 500. In other examples, computing system 102 may select phrase 536 instead of phrase 516. In this case, sending the maintenance reminder 500 to the second computing system 108 may include sending the selected phrase 508 , the selected phrase 512 , the selected phrase 514 , and the selected phrase 516 as part of the maintenance reminder 500 .

[0126] Method 400 may also involve determining that the second process is not a visual inspection process, and selecting the first phrase based on determining that the second process is not a visual inspection process. In this case, the first process described by the first phrase may be a process that includes a visual inspection of a component of the second vehicle.

[0127] For example, computing system 102 may determine that the process "monitoring crankshaft position sensor signal" as described by phrase 516 is not a visual inspection process. In response, computing system 102 may select phrase 512 to include in maintenance prompt 500 because the process "visual inspection" described by phrase 512 is a visual inspection process.

[0128] Method 400 may also involve determining that neither the first process nor the second process is a visual inspection process, and based on determining that neither the first process nor the second process is a visual inspection process, selecting a phrase stored by the first computing system that (i) is associated with a symptom and a component of the first vehicle; and (ii) describes the visual inspection process. In this case, sending the maintenance reminder may include sending the phrase describing the visual inspection process to the second computing system.

[0129] For example, computing system 102 may determine that neither the process "monitoring crankshaft position sensor signal" of phrase 516 nor the process "monitoring engine speed parameter" of phrase 508 is a visual inspection process. Therefore, computing system 102 may select phrase 512 to include in maintenance reminder 500 because the process "visual inspection" described by phrase 512 is a visual inspection process. Sometimes, describing a visual inspection process in maintenance reminder 500 may allow a maintenance technician to easily repair the first vehicle by performing a visual inspection.

[0130] In some examples, computing system 102 may determine that phrase 508 is the least recently selected phrase of phrases 508 and 528. Similarly, computing system 102 may determine that phrase 512 is the least recently selected phrase of phrases 512 and 532. Additionally, computing system 102 may determine that phrase 514 is the least recently selected phrase of phrases 514 and 534. Furthermore, computing system 102 may determine that phrase 516 is the least recently selected phrase of phrases 516 and 536. Based on these determinations, computing system 102 may include phrases 508, 512, 514, and 516 as part of maintenance tip 500 sent to computing system 108.

[0131] By further example, phrases 508, 512, and / or 514 may be listed before phrase 516 within maintenance tip 500. Since phrases 508, 512, and 514 are non-condemning phrases and phrase 516 is a condemning phrase, a maintenance technician operating computing system 108 may view phrases 508, 512, and 514 before phrase 516 and decide to perform the processes described by phrases 508, 512, and 514, respectively, before performing the process described by phrase 516. This may allow the maintenance technician to discover a "simple fix" (if possible) for the symptom of the first vehicle before performing a more complex or cumbersome process.

[0132] In this manner, any non-indictive phrases (e.g., phrases 508, 512, and 514) selected for inclusion in the maintenance prompt 500 will generally appear within the maintenance prompt 500 before any indictive phrases (e.g., phrase 516) selected for inclusion in the maintenance prompt 500. The plurality of phrases selected for inclusion in the maintenance prompt 500 may be ranked based on one or more of: (i) the monetary cost of performing the corresponding procedure, (ii) the estimated time required to perform the corresponding procedure, and (iii) the complexity of the corresponding procedure.

[0133] For example, after selecting phrases 508, 512, and 514 for inclusion in maintenance reminder 500, computing system 102 may determine an order for phrases 508, 512, and 514 based on respective one or more of: (i) a monetary cost to perform the respective processes described by phrases 508, 512, and 514, (ii) an estimated respective time required to perform the respective processes described by phrases 508, 512, and 514, and (iii) a complexity of the respective processes described by phrases 508, 512, and 514. Figure 5 In the example depicted in , phrase 508 is listed first, phrase 512 is listed second, and phrase 514 is listed third. This order may reflect the overall cost, time, and complexity of performing the respective processes of phrases 508, 512, and 514.

[0134] In some examples, computing system 102 may identify phrases 512 and 532 as being associated with the make, model, or year of manufacture of the first vehicle and the symptoms of the first vehicle based on reviewing data fields “make,” “model,” “year,” and “symptoms” of maintenance record group 612. In some examples, the threshold amount of maintenance records may be 1,200 (although other examples are possible). By reviewing data table 600, computing system 102 may determine that phrases 512 and 532 correspond to 1,500 maintenance records, and based on this determination, computing system 102 may include phrase 512 or 532 within maintenance reminder 500. In some examples, phrase 508 or phrase 528 may not be included within maintenance reminder 500 because maintenance record group 608 only corresponds to 1,000 maintenance records (less than 1,200).

[0135] By further example, computing system 102 may identify phrases 516, 536, 520, and 540 as being associated with the make, model, or year of manufacture of the first vehicle and the symptoms of the first vehicle based on reviewing the data fields “make,” “model,” “year,” and “symptoms” of maintenance record groups 616 and 620. Computing system 102 may determine that phrases 516 and 536 correspond to 1,500 maintenance records, while phrases 520 and 540 correspond to only 1,300 maintenance records. Based on this determination, computing system 102 may include phrases 516 or 536 in maintenance reminder 500 instead of phrases 520 or 540 because 1,500 is greater than 1,300.

[0136] IV. Conclusion

[0137] Exemplary embodiments have been described above. Those skilled in the art will appreciate that changes and modifications may be made to the described embodiments without departing from the true scope of the invention as defined by the claims.

[0138] Further embodiments based on the features or functions described herein may be embodied as a non-transitory computer-readable medium storing program instructions which, when executed by a processor of a machine, cause the machine to perform a set of functions including the features or functions of the various aspects and embodiments described herein.

[0139] Therefore, embodiments of the present disclosure may be directed to one of the Enumerated Example Embodiments (EEE) listed below.

[0140] EEE 1 is a computer-readable medium storing instructions that, when executed by a first computing system, cause the first computing system to perform functions including: receiving a message identifying a symptom of a first vehicle from a second computing system; and sending a maintenance reminder to the second computing system, wherein the maintenance reminder includes: a first phrase describing a first process performed on a second vehicle that exhibits the symptom, wherein the first process performed on the second vehicle produces a result that is insufficient to determine that a component of the second vehicle associated with the symptom is defective; and a second phrase describing a second process performed on a given vehicle, wherein the given vehicle is (i) the second vehicle; or (ii) a third vehicle that also exhibits the symptom, wherein the second process performed on the given vehicle produces a result that is sufficient to determine that a component of the given vehicle associated with the symptom is defective, and wherein the component of the given vehicle is equivalent to a component of the second vehicle.

[0141] EEE 2 is a computer-readable medium of EEE 1, and the functions also include: generating a maintenance reminder by generating (i) a first phrase and (ii) a second phrase, wherein sending the maintenance reminder to the second computing system includes sending the generated first phrase and the generated second phrase to the second computing system.

[0142] EEE 3 is a computer-readable medium of EEE 2, and the functions also include: identifying first data (i) stored by the first computing system and (ii) associated with symptoms and components of a second vehicle, wherein generating a first phrase includes inserting the first data into a first phrase template stored by the first computing system; and identifying second data (i) stored by the first computing system and (ii) associated with symptoms and components of a given vehicle, wherein generating a second phrase includes inserting the second data into a second phrase template stored by the first computing system.

[0143] EEE 4 is a computer readable medium of EEE 3, wherein the message identifies at least one of a make, model, or year of manufacture of the first vehicle.

[0144] EEE 5 is a computer readable medium of EEE 4, wherein identifying the first data includes identifying data associated with at least one of a make, model, or year of manufacture of the first vehicle.

[0145] EEE 6 is a computer readable medium of EEE 4, wherein identifying the second data includes identifying data associated with at least one of a make, model, or year of manufacture of the first vehicle.

[0146] EEE 7 is the computer readable medium of any one of EEEs 3-6, the functions further comprising, before generating the first phrase, selecting a first phrase template from a plurality of phrase templates stored by the first computing system.

[0147] EEE 8 is a computer readable medium of EEE 7, and the functions also include: determining that the first phrase template is the least recently selected phrase template of any one of the multiple phrase templates, wherein selecting the first phrase template includes selecting the first phrase template based on determining that the first phrase template is the least recently selected phrase template of any one of the multiple phrase templates.

[0148] EEE 9 is a computer readable medium of EEE 7, wherein selecting the first phrase template comprises randomly selecting the first phrase template from a plurality of phrase templates.

[0149] EEE 10 is the computer readable medium of any one of EEEs 3-9, the functions further comprising, before generating the second phrase, selecting a second phrase template from a plurality of phrase templates stored by the first computing system.

[0150] EEE 11 is a computer-readable medium of EEE 10, and the function also includes: determining that the second phrase template is the least recently selected phrase template of any one of the multiple phrase templates, wherein selecting the second phrase template includes selecting the second phrase template based on determining that the second phrase template is the least recently selected phrase template of any one of the multiple phrase templates.

[0151] The EEE 12 is a computer readable medium of the EEE 10, wherein selecting the second phrase template includes randomly selecting the second phrase template from a plurality of phrase templates.

[0152] EEE 13 is a computer-readable medium of any one of EEE 3-12, wherein identifying the first data includes determining that the first data corresponds to a given data field of the first phrase template, and wherein inserting the first data into the first phrase template includes inserting the first data into the given data field of the first phrase template.

[0153] EEE 14 is a computer-readable medium of any one of EEEs 3-4, wherein the first data includes data identifying one or more of the following: (i) components of the second vehicle; (ii) the first process; (iii) results generated by the first process performed on the second vehicle; and (iv) a tool for performing the first process.

[0154] EEE 15 is a computer-readable medium of any one of EEE 3-5, wherein identifying the second data includes determining that the second data corresponds to a given data field of the second phrase template, and wherein inserting the second data into the second phrase template includes inserting the second data into the given data field of the second phrase template.

[0155] EEE 16 is a computer-readable medium of any one of EEEs 3-15, wherein the second data includes data identifying one or more of the following: (i) components of a given vehicle; (ii) a second process; (iii) results generated by the second process performed on the given vehicle; and (iv) a tool for performing the second process.

[0156] EEE 17 is a computer-readable medium of any one of EEEs 1-16, and the functions also include: determining that neither the first process nor the second process is a visual inspection process; based on determining that neither the first process nor the second process is a visual inspection process, identifying third data that is (i) stored by the first computing system, (ii) associated with symptoms and components of the first vehicle, and (iii) associated with the visual inspection process; and generating a third phrase by inserting the third data into a third phrase template stored by the first computing system, wherein sending the maintenance reminder includes sending the generated third phrase to the second computing system.

[0157] EEE 18 is a computer readable medium of any one of EEEs 1-16, the functions further comprising: determining that the second process is not a visual inspection process, wherein identifying the first data includes identifying data associated with the visual inspection process.

[0158] EEE 19 is a computer-readable medium of EEE 1, wherein the message identifies at least one of a make, model, or year of manufacture of a first vehicle, and the functions further include: identifying first data stored by a first computing system, the first data being associated with at least one of: (i) a make, model, or year of manufacture of a second vehicle; (ii) a symptom of the second vehicle; and (iii) a first process; and determining that the first data corresponds to at least a predetermined amount of maintenance records stored by the first computing system, wherein the first phrase includes the first data.

[0159] EEE 20 is a computer-readable medium of EEE 1, wherein the message identifies at least one of a make, model, or year of manufacture of a first vehicle, and the functions further include: identifying second data stored by the first computing system, the second data being associated with at least one of: (i) a make, model, or year of manufacture of a given vehicle; (ii) a symptom of a given vehicle; and (iii) a second process; and determining that the second data corresponds to at least a predetermined amount of maintenance records stored by the first computing system, wherein the second phrase includes the second data.

[0160] EEE 21 is a computer-readable medium of EEE 1, and the functions also include: identifying a first plurality of phrases stored by a first computing system, each of the first plurality of phrases (i) being associated with symptoms and components of a second vehicle, (ii) conveying information equivalent to information conveyed by each of the other phrases of the first plurality of phrases, and (iii) including syntax different from all other phrases of the first plurality of phrases; selecting a first phrase from the first plurality of phrases; identifying a second plurality of phrases stored by the first computing system, each of the second plurality of phrases (i) being associated with symptoms and components of a given vehicle, (ii) conveying information equivalent to information conveyed by each of the other phrases of the second plurality of phrases, and (iii) including syntax different from all other phrases of the second plurality of phrases; and selecting a second phrase from the second plurality of phrases, wherein sending the maintenance reminder to the second computing system includes sending the selected first phrase and the selected second phrase.

[0161] EEE 22 is a computer-readable medium of EEE 21, and the functions also include: determining that the second process is not a visual inspection process; and wherein selecting the first phrase includes selecting the first phrase based on determining that the second process is not a visual inspection process, wherein the first process described by the first phrase is a process that includes a visual inspection of a component of the second vehicle.

[0162] EEE 23 is a computer-readable medium of EEE 21, and the functions also include: determining that neither the first process nor the second process is a visual inspection process; based on determining that neither the first process nor the second process is a visual inspection process, selecting a third phrase stored by the first computing system, the third phrase (i) being associated with a symptom and a component of the first vehicle, and (ii) describing the visual inspection process, wherein sending the maintenance reminder includes sending the third phrase to the second computing system.

[0163] EEE 24 is the computer-readable medium of any one of EEEs 21 and 23, wherein selecting the first phrase comprises randomly selecting the first phrase from the first plurality of phrases.

[0164] EEE 25 is the computer-readable medium of any one of EEEs 21-24, wherein selecting the second phrase comprises randomly selecting the second phrase from the second plurality of phrases.

[0165] EEE 26 is a computer readable medium of EEE 21, and the functions also include: determining that the first phrase is the least recently selected phrase of any one of the first plurality of phrases, wherein selecting the first phrase includes selecting the first phrase based on determining that the first phrase is the least recently selected phrase of any one of the first plurality of phrases.

[0166] EEE 27 is a computer-readable medium of any one of EEEs 621-24 and 26, and the functions also include: determining that the second phrase is the least recently selected phrase of any one of the second plurality of phrases, wherein selecting the second phrase includes selecting the second phrase based on determining that the second phrase is the least recently selected phrase of any one of the second plurality of phrases.

[0167] EEE 28 is a computer-readable medium of any one of EEEs 1-27, wherein the first phrase is listed before the second phrase in the maintenance tip.

[0168] EEE 29 is a computer-readable medium of EEE 28, wherein the maintenance tip further comprises one or more additional phrases listed before the second phrase in the maintenance tip, wherein the one or more additional phrases describe a respective procedure performed on a respective vehicle, and wherein the first phrase and the one or more additional phrases are listed in the maintenance tip in an order based on one or more of: (i) a monetary cost to perform the respective procedure, (ii) an estimated time required to perform the respective procedure, and (iii) a complexity of the respective procedure.

[0169] EEE 30 is a computer-readable medium of EEE 1, wherein the message identifies at least one of a make, model, or year of manufacture of a first vehicle, and the functions further include: identifying a first plurality of phrases stored by a first computing system, each of the first plurality of phrases being associated with at least one of a make, model, or year of manufacture of the first vehicle and a symptom of the first vehicle, wherein the first plurality of phrases includes a first phrase; and determining that the first phrase corresponds to at least a predetermined amount of maintenance records stored by the first computing system, wherein sending the maintenance reminder to the second computing system includes sending the first phrase based on determining that the first phrase corresponds to at least a predetermined amount of maintenance records stored by the first computing system.

[0170] EEE 31 is a computer readable medium of EEE 30, wherein the first plurality of phrases describe a respective process performed on the respective vehicle that produces results insufficient to determine that a component of the respective vehicle associated with the symptom is defective.

[0171] EEE 32 is a computer-readable medium of EEE 1, wherein the message identifies at least one of a make, model, or year of manufacture of the first vehicle, and the functions further include: identifying a second plurality of phrases stored by the first computing system, each of the second plurality of phrases being associated with at least one of a make, model, or year of manufacture of the first vehicle and a symptom of the first vehicle, wherein the second plurality of phrases includes the second phrase; and determining that the second phrase corresponds to at least as many maintenance records stored by the first computing system as any other phrase in the second plurality of phrases, wherein sending the maintenance reminder to the second computing system includes sending the second phrase based on determining that the second phrase corresponds to at least as many maintenance records stored by the first computing system as any other phrase in the second plurality of phrases.

[0172] EEE 33 is a computer readable medium of EEE 32, wherein the second plurality of phrases describe a respective process performed on the respective vehicle, the respective process producing a result sufficient to determine that a component of the respective vehicle is defective.

[0173] EEE 34 is the computer-readable medium of any one of EEEs 1-33, wherein the computer-readable medium is a non-transitory computer-readable medium.

[0174] EEE 35 is a method performed by a first computing system, the method comprising: receiving a message identifying a symptom of a first vehicle from a second computing system; and sending a maintenance reminder to the second computing system, wherein the maintenance reminder comprises: a first phrase describing a first process performed on a second vehicle presenting the symptom, wherein the first process performed on the second vehicle produces a result insufficient to determine that a component of the second vehicle associated with the symptom is defective; and a second phrase describing a second process performed on a given vehicle, wherein the given vehicle is (i) the second vehicle; or (ii) a third vehicle also presenting the symptom, wherein the second process performed on the given vehicle produces a result sufficient to determine that a component of the given vehicle associated with the symptom is defective, and wherein the component of the given vehicle is equivalent to a component of the second vehicle.

[0175] EEE 36 is the method of EEE 35, further comprising: generating a maintenance reminder by generating (i) a first phrase, and (ii) a second phrase, wherein sending the maintenance reminder to the second computing system comprises sending the generated first phrase and the generated second phrase to the second computing system.

[0176] EEE 37 is the method of EEE 36, further comprising: identifying first data (i) stored by the first computing system and (ii) associated with symptoms and components of a second vehicle, wherein generating the first phrase comprises inserting the first data into a first phrase template stored by the first computing system; and identifying second data (i) stored by the first computing system and (ii) associated with symptoms and components of a given vehicle, wherein generating the second phrase comprises inserting the second data into a second phrase template stored by the first computing system.

[0177] EEE 38 is the method of EEE 37 , wherein the message identifies at least one of a make, model, or year of manufacture of the first vehicle.

[0178] EEE 39 is the method of EEE 38 , wherein identifying the first data includes identifying data associated with at least one of a make, model, or year of manufacture of the first vehicle.

[0179] EEE 40 is the method of EEE 38 , wherein identifying the second data includes identifying data associated with at least one of a make, model, or year of manufacture of the first vehicle.

[0180] EEE 41 is the method of any one of EEEs 37-40, further comprising, before generating the first phrase, selecting a first phrase template from a plurality of phrase templates stored in the first computing system.

[0181] EEE 42 is the method of EEE 41, further comprising: determining that the first phrase template is the least recently selected phrase template of any one of the plurality of phrase templates, wherein selecting the first phrase template comprises selecting the first phrase template based on determining that the first phrase template is the least recently selected phrase template of any one of the plurality of phrase templates.

[0182] EEE 43 is the method of EEE 41, wherein selecting the first phrase template comprises randomly selecting the first phrase template from a plurality of phrase templates.

[0183] EEE 44 is the method of any of EEEs 37-43, further comprising, before generating the second phrase, selecting a second phrase template from a plurality of phrase templates stored by the first computing system.

[0184] EEE 45 is the method of EEE 44, further comprising: determining that the second phrase template is the least recently selected phrase template of any one of the plurality of phrase templates, wherein selecting the second phrase template comprises selecting the second phrase template based on determining that the second phrase template is the least recently selected phrase template of any one of the plurality of phrase templates.

[0185] EEE 46 is the method of EEE 44, wherein selecting the second phrase template comprises randomly selecting the second phrase template from the plurality of phrase templates.

[0186] EEE 47 is a method of any one of EEEs 37-46, wherein identifying the first data includes determining that the first data corresponds to a given data field of the first phrase template, and wherein inserting the first data into the first phrase template includes inserting the first data into the given data field of the first phrase template.

[0187] EEE 48 is a method of any one of EEEs 37-47, wherein the first data includes data identifying one or more of: (i) a component of the second vehicle; (ii) the first process; (iii) a result produced by the first process performed on the second vehicle; and (iv) a tool for performing the first process.

[0188] EEE 49 is a method of any one of EEEs 37-48, wherein identifying the second data includes determining that the second data corresponds to a given data field of the second phrase template, and wherein inserting the second data into the second phrase template includes inserting the second data into the given data field of the second phrase template.

[0189] EEE 50 is a method of any one of EEEs 37-49, wherein the second data includes data identifying one or more of: (i) components of a given vehicle; (ii) a second process; (iii) results produced by the second process performed on the given vehicle; and (iv) a tool for performing the second process.

[0190] EEE 51 is a method of any one of EEEs 35-50, further comprising: determining that neither the first process nor the second process is a visual inspection process; based on determining that neither the first process nor the second process is a visual inspection process, identifying third data that is (i) stored by the first computing system, (ii) associated with symptoms and components of the first vehicle, and (iii) associated with the visual inspection process; and generating a third phrase by inserting the third data into a third phrase template stored by the first computing system, wherein sending the maintenance reminder includes sending the generated third phrase to the second computing system.

[0191] EEE 52 is the method of any one of EEEs 35-50, further comprising: determining that the second process is not a visual inspection process, wherein identifying the first data includes identifying data associated with the visual inspection process.

[0192] EEE 53 is the method of EEE 35, wherein the message identifies at least one of a make, model, or year of manufacture of a first vehicle, and the method further comprises: identifying first data stored by a first computing system, the first data being associated with: (i) at least one of a make, model, or year of manufacture of a second vehicle; (ii) a symptom of the second vehicle; and (iii) a first process; and determining that the first data corresponds to at least a predetermined amount of maintenance records stored by the first computing system, wherein the first phrase includes the first data.

[0193] EEE 54 is the method of EEE 35, wherein the message identifies at least one of a make, model, or year of manufacture of a first vehicle, and the method further comprises: identifying second data stored by the first computing system, the second data being associated with: (i) at least one of a make, model, or year of manufacture of a given vehicle; (ii) a symptom of the given vehicle; and (iii) a second process; and determining that the second data corresponds to at least a predetermined amount of service records stored by the first computing system, wherein the second phrase includes the second data.

[0194] EEE 55 is the method of EEE 35, further comprising: identifying a first plurality of phrases stored by a first computing system, each of the first plurality of phrases (i) being associated with symptoms and components of a second vehicle, (ii) conveying information equivalent to information conveyed by each of the other phrases in the first plurality of phrases, and (iii) including syntax different from all other phrases in the first plurality of phrases; selecting a first phrase from the first plurality of phrases; identifying a second plurality of phrases stored by the first computing system, each of the second plurality of phrases (i) being associated with symptoms and components of a given vehicle, (ii) conveying information equivalent to information conveyed by each of the other phrases in the second plurality of phrases, and (iii) including syntax different from all other phrases in the second plurality of phrases; and selecting a second phrase from the second plurality of phrases, wherein sending the maintenance reminder to the second computing system comprises sending the selected first phrase and the selected second phrase.

[0195] EEE 56 is the method of EEE 55, further comprising: determining that the second process is not a visual inspection process; and wherein selecting the first phrase comprises selecting the first phrase based on determining that the second process is not a visual inspection process, wherein the first process described by the first phrase is a process including a visual inspection of a component of the second vehicle.

[0196] EEE 57 is the method of EEE 55, further comprising: determining that neither the first process nor the second process is a visual inspection process; based on determining that neither the first process nor the second process is a visual inspection process, selecting a third phrase stored by the first computing system, the third phrase (i) being associated with a symptom and a component of the first vehicle, and (ii) describing the visual inspection process, wherein sending the maintenance reminder includes sending the third phrase to the second computing system.

[0197] EEE58 is the method of any of EEEs 55 and 57, wherein selecting the first phrase comprises randomly selecting the first phrase from the first plurality of phrases.

[0198] EEE 59 is the method of any one of EEEs 55-58, wherein selecting the second phrase includes randomly selecting the second phrase from the second plurality of phrases.

[0199] EEE 60 is the method of EEE 55, further comprising: determining that the first phrase is the least recently selected phrase of any of the first plurality of phrases, wherein selecting the first phrase comprises selecting the first phrase based on determining that the first phrase is the least recently selected phrase of any of the first plurality of phrases.

[0200] EEE 61 is the method of any one of EEEs 655-58 and 60, further comprising: determining that the second phrase is the least recently selected phrase of any one of the second plurality of phrases, wherein selecting the second phrase comprises selecting the second phrase based on determining that the second phrase is the least recently selected phrase of any one of the second plurality of phrases.

[0201] EEE 62 is the method of any one of EEEs 35-61, wherein the first phrase is listed before the second phrase in the maintenance prompt.

[0202] EEE 63 is the method of EEE 62, wherein the maintenance reminder further includes one or more additional phrases listed before the second phrase in the maintenance reminder, wherein the one or more additional phrases describe a corresponding procedure that was performed on the corresponding vehicle, and wherein the first phrase and the one or more additional phrases are listed in the maintenance reminder in an order based on one or more of: (i) a monetary cost to perform the corresponding procedure, (ii) an estimated time required to perform the corresponding procedure, and (iii) a complexity of the corresponding procedure.

[0203] EEE 64 is the method of EEE 35, wherein the message identifies at least one of a make, model, or year of manufacture of a first vehicle, the method further comprising: identifying a first plurality of phrases stored by a first computing system, each of the first plurality of phrases being associated with at least one of a make, model, or year of manufacture of the first vehicle and a symptom of the first vehicle, wherein the first plurality of phrases includes a first phrase; and determining that the first phrase corresponds to at least a predetermined amount of maintenance records stored by the first computing system, wherein sending the maintenance reminder to the second computing system includes sending the first phrase based on determining that the first phrase corresponds to at least a predetermined amount of maintenance records stored by the first computing system.

[0204] EEE 65 is the method of EEE 64, wherein the first plurality of phrases describe a respective process performed on the respective vehicle that produces results insufficient to determine that a component of the respective vehicle associated with the symptom is defective.

[0205] EEE 66 is the method of EEE 35, wherein the message identifies at least one of a make, model, or year of manufacture of the first vehicle, the method further comprising: identifying a second plurality of phrases stored by the first computing system, each of the second plurality of phrases being associated with at least one of a make, model, or year of manufacture of the first vehicle and a symptom of the first vehicle, wherein the second plurality of phrases includes the second phrase; and determining that the second phrase corresponds to at least as many maintenance records stored by the first computing system as any other phrase in the second plurality of phrases, wherein sending the maintenance reminder to the second computing system includes sending the second phrase based on determining that the second phrase corresponds to at least as many maintenance records stored by the first computing system as any other phrase in the second plurality of phrases.

[0206] EEE 67 is the method of EEE 66, wherein the second plurality of phrases describe a respective process performed on the respective vehicle, the respective process producing a result sufficient to determine that a component of the respective vehicle is defective.

[0207] EEE 68 is a computing system comprising: one or more processors; and a non-transitory computer-readable medium storing instructions that, when executed by the one or more processors, cause the computing system to perform functions comprising the following steps: receiving a message identifying a symptom of a first vehicle from an additional computing system; and sending a maintenance reminder to a second computing system, wherein the maintenance reminder comprises: a first phrase describing a first process performed on a second vehicle presenting the symptom, wherein the first process performed on the second vehicle produces a result insufficient to determine that a component of the second vehicle associated with the symptom is defective; and a second phrase describing a second process performed on a given vehicle, wherein the given vehicle is (i) the second vehicle; or (ii) a third vehicle also presenting the symptom, wherein the second process performed on the given vehicle produces a result sufficient to determine that a component of the given vehicle associated with the symptom is defective, and wherein the component of the given vehicle is equivalent to a component of the second vehicle.

[0208] EEE 69 is the computing system of EEE 68, and the function also includes: generating a maintenance reminder by generating (i) a first phrase, and (ii) a second phrase, wherein sending the maintenance reminder to the second computing system includes sending the generated first phrase and the generated second phrase to the second computing system.

[0209] EEE 70 is the computing system of EEE 69, and the functions also include: identifying first data (i) stored by the computing system and (ii) associated with symptoms and components of a second vehicle, wherein generating a first phrase includes inserting the first data into a first phrase template stored by the computing system; and identifying second data (i) stored by the computing system; and (ii) associated with symptoms and components of a given vehicle, wherein generating a second phrase includes inserting the second data into a second phrase template stored by the computing system.

[0210] EEE 71 is the computing system of EEE 70 , wherein the message identifies at least one of a make, model, or year of manufacture of the first vehicle.

[0211] EEE 72 is the computing system of EEE 71 , wherein identifying the first data includes identifying data associated with at least one of a make, model, or year of manufacture of the first vehicle.

[0212] EEE 73 is the computing system of EEE 71 , wherein identifying the second data includes identifying data associated with at least one of a make, model, or year of manufacture of the first vehicle.

[0213] EEE 74 is the computing system of any one of EEEs 70-73, and the functions further include selecting a first phrase template from a plurality of phrase templates stored by the computing system before generating the first phrase.

[0214] EEE 75 is the computing system of EEE 74, and the function also includes: determining that the first phrase template is the least recently selected phrase template of any one of the multiple phrase templates, wherein selecting the first phrase template includes selecting the first phrase template based on determining that the first phrase template is the least recently selected phrase template of any one of the multiple phrase templates.

[0215] EEE 76 is the computing system of EEE 74, wherein selecting the first phrase template includes randomly selecting the first phrase template from a plurality of phrase templates.

[0216] EEE 77 is the computing system of any one of EEEs 70-76, the function further comprising selecting a second phrase template from a plurality of phrase templates stored by the computing system before generating the second phrase.

[0217] EEE 78 is the computing system of EEE 77, and the function also includes: determining that the second phrase template is the least recently selected phrase template of any one of the multiple phrase templates, wherein selecting the second phrase template includes selecting the second phrase template based on determining that the second phrase template is the least recently selected phrase template of any one of the multiple phrase templates.

[0218] EEE 79 is the computing system of EEE 77, wherein selecting the second phrase template comprises randomly selecting the second phrase template from a plurality of phrase templates.

[0219] EEE 80 is a computing system of any one of EEEs 70-79, wherein identifying the first data includes determining that the first data corresponds to a given data field of the first phrase template, and wherein inserting the first data into the first phrase template includes inserting the first data into the given data field of the first phrase template.

[0220] EEE 81 is a computing system of any one of EEE 70-80, wherein the first data includes data identifying one or more of the following: (i) components of the second vehicle; (ii) the first process; (iii) results generated by the first process performed on the second vehicle; and (iv) a tool for performing the first process.

[0221] EEE 82 is a computing system of any one of EEE 70-81, wherein identifying the second data includes determining that the second data corresponds to a given data field of the second phrase template, and wherein inserting the second data into the second phrase template includes inserting the second data into the given data field of the second phrase template.

[0222] EEE 83 is a computing system of any one of EEE 70-82, wherein the second data includes data identifying one or more of the following: (i) components of a given vehicle; (ii) a second process; (iii) results produced by the second process performed on the given vehicle; and (iv) a tool for performing the second process.

[0223] EEE 84 is a computing system of any one of EEE 68-83, and the function also includes: determining that neither the first process nor the second process is a visual inspection process; based on determining that neither the first process nor the second process is a visual inspection process, identifying third data that is (i) stored by the computing system, (ii) associated with symptoms and components of the first vehicle, and (iii) associated with the visual inspection process; and generating a third phrase by inserting the third data into a third phrase template stored by the computing system, wherein sending the maintenance reminder includes sending the generated third phrase to the second computing system.

[0224] EEE 85 is the computing system of any one of EEE 68-83, the functions further comprising: determining that the second process is not a visual inspection process, wherein identifying the first data includes identifying data associated with the visual inspection process.

[0225] EEE 86 is the computing system of EEE 68, wherein the message identifies at least one of a make, model, or year of manufacture of a first vehicle, and the functions further include: identifying first data stored by the computing system, the first data being associated with: (i) at least one of a make, model, or year of manufacture of a second vehicle; (ii) a symptom of the second vehicle; and (iii) a first process; and determining that the first data corresponds to at least a predetermined amount of maintenance records stored by the computing system, wherein the first phrase includes the first data.

[0226] EEE 87 is the computing system of EEE 68, wherein the message identifies at least one of a make, model, or year of manufacture of a first vehicle, and the functions further include: identifying second data stored by the computing system, the second data being associated with: (i) at least one of a make, model, or year of manufacture of a given vehicle; (ii) a symptom of the given vehicle; and (iii) a second process; and determining that the second data corresponds to at least a predetermined amount of maintenance records stored by the computing system, wherein the second phrase includes the second data.

[0227] EEE 88 is a computing system of EEE 68, and the functions also include: identifying a first plurality of phrases stored by the computing system, each of the first plurality of phrases (i) being associated with symptoms and components of a second vehicle, (ii) conveying information equivalent to information conveyed by each of the other phrases in the first plurality of phrases, and (iii) including syntax different from all other phrases in the first plurality of phrases; selecting a first phrase from the first plurality of phrases; identifying a second plurality of phrases stored by the computing system, each of the second plurality of phrases (i) being associated with symptoms and components of a given vehicle, (ii) conveying information equivalent to information conveyed by each of the other phrases in the second plurality of phrases, and (iii) including syntax different from all other phrases in the second plurality of phrases; and selecting a second phrase from the second plurality of phrases, wherein sending the maintenance reminder to the second computing system includes sending the selected first phrase and the selected second phrase.

[0228] EEE 89 is the computing system of EEE 88, and the function also includes: determining that the second process is not a visual inspection process; and wherein selecting the first phrase includes selecting the first phrase based on determining that the second process is not a visual inspection process, wherein the first process described by the first phrase is a process that includes visual inspection of components of the second vehicle.

[0229] EEE 90 is a computing system of EEE 88, and the functions also include: determining that neither the first process nor the second process is a visual inspection process; based on determining that neither the first process nor the second process is a visual inspection process, selecting a third phrase stored by the computing system, the third phrase (i) being associated with a symptom and a component of the first vehicle, and (ii) describing the visual inspection process, wherein sending the maintenance reminder includes sending the third phrase to the second computing system.

[0230] EEE 91 is the computing system of any of EEEs 88 and 90, wherein selecting the first phrase comprises randomly selecting the first phrase from the first plurality of phrases.

[0231] EEE 92 is the computing system of any one of EEEs 88-91, wherein selecting the second phrase comprises randomly selecting the second phrase from the second plurality of phrases.

[0232] EEE 93 is the computing system of EEE 88, and the function also includes: determining that the first phrase is the least recently selected phrase of any one of the first plurality of phrases, wherein selecting the first phrase includes selecting the first phrase based on determining that the first phrase is the least recently selected phrase of any one of the first plurality of phrases.

[0233] EEE 94 is a computing system of any one of EEEs 688-91 and 93, and the functions also include: determining that the second phrase is the least recently selected phrase of any one of the second plurality of phrases, wherein selecting the second phrase includes selecting the second phrase based on determining that the second phrase is the least recently selected phrase of any one of the second plurality of phrases.

[0234] EEE 95 is a computing system of any one of EEE 68-94, wherein the first phrase is listed before the second phrase in the maintenance prompt.

[0235] EEE 96 is the computing system of EEE 95, wherein the maintenance reminder further includes one or more additional phrases listed before the second phrase in the maintenance reminder, wherein the one or more additional phrases describe a respective procedure performed on the respective vehicle, and wherein the first phrase and the one or more additional phrases are listed in the maintenance reminder in an order based on one or more of: (i) a monetary cost to perform the respective procedure, (ii) an estimated time required to perform the respective procedure, and (iii) a complexity of the respective procedure.

[0236] EEE 97 is the computing system of EEE 68, wherein the message identifies at least one of a make, model, or year of manufacture of a first vehicle, and the functions further include: identifying a first plurality of phrases stored by the computing system, each of the first plurality of phrases being associated with at least one of a make, model, or year of manufacture of the first vehicle and a symptom of the first vehicle, wherein the first plurality of phrases includes a first phrase; and determining that the first phrase corresponds to at least a predetermined amount of maintenance records stored by the computing system, wherein sending the maintenance reminder to the second computing system includes sending the first phrase based on determining that the first phrase corresponds to at least a predetermined amount of maintenance records stored by the computing system.

[0237] EEE 98 is the computing system of EEE 97, wherein the first plurality of phrases describe respective processes executed on the respective vehicle that produce results insufficient to determine that a component of the respective vehicle associated with the symptom is defective.

[0238] EEE 99 is the computing system of EEE 68, wherein the message identifies at least one of a make, model, or year of manufacture of a first vehicle, and the functions further include: identifying a second plurality of phrases stored by the computing system, each of the second plurality of phrases being associated with at least one of a make, model, or year of manufacture of the first vehicle and a symptom of the first vehicle, wherein the second plurality of phrases includes the second phrase; and determining that the second phrase corresponds to at least as many maintenance records stored by the computing system as any other phrase in the second plurality of phrases, wherein sending the maintenance reminder to the second computing system includes sending the second phrase based on determining that the second phrase corresponds to at least as many maintenance records stored by the computing system as any other phrase in the second plurality of phrases.

[0239] EEE 100 is a computing system of EEE 32, wherein the second plurality of phrases describe a respective process executed on a respective vehicle that produces a result sufficient to determine that a component of the respective vehicle is defective.

Claims

1. A method performed by a vehicle repair tool, comprising: At least one processor and a network interface, wherein the at least one processor is configured to diagnose the specific vehicle by checking a diagnostic problem code (DTC) set in the specific vehicle, and wherein the network interface is connected to the at least one processor and is operably connected to a wired communication link on the specific vehicle, the method comprising: receiving a set of search terms by the at least one processor, wherein the set of search terms includes a first term indicating at least a portion of a vehicle type identifier associated with the specific vehicle and a second term indicating a symptom exhibited by the specific vehicle; wirelessly sending a request for a maintenance reminder by the network interface to a communication network including a computing system outside the specific vehicle, wherein the request includes the set of search terms; and in response to the request, receiving a maintenance reminder from the specific vehicle via the network interface via the communication network. the computing system external to the processor wirelessly receiving the maintenance reminder; and displaying the maintenance reminder through a user interface connected to the at least one processor, wherein the maintenance reminder includes a first phrase and a second phrase, wherein the first phrase describes a first process performed on a second vehicle exhibiting the symptom, wherein the first process performed on the second vehicle produces a result insufficient to determine that a component of the second vehicle associated with the symptom is defective, wherein the second phrase describes a second process performed on a given vehicle, the given vehicle being the second vehicle or a third vehicle also exhibiting the symptom, and wherein the second process performed on the given vehicle produces a result sufficient to determine that a component of the given vehicle associated with the symptom is defective, the component of the given vehicle being equivalent to the component of the second vehicle.

2. The method according to claim 1, further comprising: The specific vehicle is diagnosed by checking the DTC set in the specific vehicle, wherein the symptom exhibited by the specific vehicle includes the DTC.

3. The method according to claim 1, further comprising: The second item is displayed via the user interface, the second item being indicative of the symptom exhibited by the particular vehicle, wherein receiving the set of search terms includes receiving a selection of the second item displayed via the user interface.

4. The method of claim 1, wherein the first item indicates at least one of: a year of the specific vehicle, a brand of the specific vehicle, a model of the specific vehicle, a sub-model of the specific vehicle, an engine of the specific vehicle, a system of the specific vehicle, and a configuration package of the specific vehicle.

5. The method according to claim 1, further comprising: The first term is displayed via the user interface, the first term indicating the at least a portion of the vehicle type identifier associated with the particular vehicle, wherein receiving the set of search terms includes receiving a selection of the first term displayed via the user interface.

6. The method according to claim 1, wherein: The symptom indicates that the check engine light is on or a diagnostic problem code in the particular vehicle.

7. The method according to claim 1 also includes displaying by the user interface a field for selecting vehicle identification attributes for forming a set of search terms, selecting symptom criteria for forming a portion of the set of search terms, and entering vehicle mileage or engine usage hours.

8. The method according to claim 1, further comprising: A repair order is generated by the vehicle repair tool, the repair order documenting the vehicle type identifier and the symptoms exhibited by the specific vehicle.

9. The method according to claim 1, wherein: The maintenance prompt includes at least one of the following: a title, a customer complaint phrase, a reason phrase, and a correction phrase.

10. A vehicle maintenance tool comprising: at least one processor; a network interface coupled to the at least one processor and operably connected to a wired communication link on a particular vehicle; and a user interface connected to the at least one processor, wherein the at least one processor is configured to diagnose the specific vehicle by checking a diagnostic problem code (DTC) set in the specific vehicle, and receive a set of search terms, wherein the set of search terms includes a first term indicating at least a portion of a vehicle type identifier associated with the specific vehicle and a second term indicating a symptom exhibited by the specific vehicle, wherein the network interface is configured to wirelessly send a request for a maintenance reminder to a communication network including a computing system external to the specific vehicle, wherein the request includes the set of search terms, wherein the network interface is configured to wirelessly receive the maintenance reminder from the computing system external to the specific vehicle via the communication network in response to the request, and wherein the user interface is configured to display the maintenance prompt, wherein the maintenance prompt includes a first phrase and a second phrase, wherein the first phrase describes a first procedure performed on a second vehicle exhibiting the symptom, wherein the first procedure performed on the second vehicle produces a result insufficient to determine that a component of the second vehicle associated with the symptom is defective, wherein the second phrase describes a second procedure performed on a given vehicle, the given vehicle being the second vehicle or a third vehicle also exhibiting the symptom, and wherein the second procedure performed on the given vehicle produces a result sufficient to determine that the component of the given vehicle associated with the symptom is defective, the component of the given vehicle being equivalent to the component of the second vehicle.

11. The vehicle repair tool according to claim 10, wherein: The symptoms exhibited by the particular vehicle include the DTCs.

12. The vehicle repair tool according to claim 10, wherein: The user interface is also configured to display the second item indicative of the symptom exhibited by the particular vehicle, and wherein being configured to receive the set of search terms includes being configured to receive a selection of the second item displayed via the user interface.

13. The vehicle repair tool according to claim 10, wherein: The first item indicates at least one of: a year of the specific vehicle, a brand of the specific vehicle, a model of the specific vehicle, a sub-model of the specific vehicle, an engine of the specific vehicle, a system of the specific vehicle, and a configuration package of the specific vehicle.

14. The vehicle repair tool of claim 10, wherein: The user interface is also configured to display the first item, which indicates at least a portion of the vehicle type identifier associated with the particular vehicle, wherein being configured to receive the set of search terms includes being configured to receive a selection of the first item displayed via the user interface.

15. The vehicle repair tool of claim 10, wherein: The symptom indicates that the check engine light is on or a diagnostic problem code in the particular vehicle.

16. The vehicle repair tool of claim 10, wherein: The user interface displays vehicle identification attributes selected for forming the set of search terms, symptom criteria selected for forming a portion of the set of search terms, and fields for entering vehicle mileage or engine hours.

17. The vehicle repair tool of claim 10, wherein: The vehicle service tool is configured to generate a service order documenting the vehicle type identifier and the symptom exhibited by the particular vehicle.

18. The vehicle repair tool of claim 10, wherein: The maintenance prompt includes at least one of the following: a title, a customer complaint phrase, a reason phrase, and a correction phrase.

19. A non-transitory computer-readable medium configured to store at least computer-readable instructions that, when executed by at least one processor of a vehicle service tool, cause the vehicle service tool to perform a plurality of functions, wherein: The vehicle service tool is configured to diagnose the specific vehicle by checking for a diagnostic problem code (DTC) set in the specific vehicle, wherein the vehicle service tool includes a network interface connected to the at least one processor and operably connected to a wired communication link on the specific vehicle, wherein the multiple functions include: receiving a set of search terms, wherein the set of search terms includes a first term indicating at least a portion of a vehicle type identifier associated with the specific vehicle and a second term indicating a symptom exhibited by the specific vehicle; wirelessly sending a request for a service reminder to a communication network including a computing system external to the specific vehicle, wherein the request includes the set of search terms; and wirelessly sending a request for a service reminder from the computing system external to the specific vehicle via the communication network in response to the request. receiving the maintenance prompt online; and displaying the maintenance prompt through a user interface, wherein the maintenance prompt includes a first phrase and a second phrase, wherein the first phrase describes a first process performed on a second vehicle exhibiting the symptom, wherein the first process performed on the second vehicle produces a result insufficient to determine that a component of the second vehicle associated with the symptom is defective, wherein the second phrase describes a second process performed on a given vehicle, wherein the given vehicle is the second vehicle or a third vehicle that also exhibits the symptom, and wherein the second process performed on the given vehicle produces a result sufficient to determine that the component of the given vehicle associated with the symptom is defective, the component of the given vehicle being equivalent to the component of the second vehicle.

20. The non-transitory computer readable medium of claim 19, wherein: The plurality of functions further include diagnosing the specific vehicle by checking the DTC set in the specific vehicle, wherein the symptom exhibited by the specific vehicle includes the DTC.

21. The non-transitory computer readable medium of claim 19, wherein: The plurality of functions further include displaying, via the user interface, the second item indicative of the symptom exhibited by the particular vehicle, wherein receiving the set of search terms includes receiving a selection of the second item displayed via the user interface.

22. The non-transitory computer readable medium of claim 19, wherein: The first item indicates at least one of: a year of the specific vehicle, a brand of the specific vehicle, a model of the specific vehicle, a sub-model of the specific vehicle, an engine of the specific vehicle, a system of the specific vehicle, and a configuration package of the specific vehicle.

23. The non-transitory computer readable medium of claim 19, wherein: The plurality of functions further include displaying, via the user interface, the first item indicating at least a portion of the vehicle type identifier associated with the particular vehicle, wherein receiving the set of search terms includes receiving a selection of the first item displayed via the user interface.

24. The non-transitory computer readable medium of claim 19, wherein: The symptom indicates that the check engine light is on or a diagnostic problem code in the particular vehicle.

25. The non-transitory computer readable medium of claim 19, wherein: The plurality of functions also includes displaying by the user interface vehicle identification attributes selected for forming the set of search terms, symptom criteria selected for forming a portion of the set of search terms, and fields for entering vehicle mileage or engine hours.

26. The non-transitory computer readable medium of claim 19, wherein: The plurality of functions further includes generating, by the vehicle repair tool, a repair order documenting the vehicle type identifier and the symptoms exhibited by the particular vehicle.

27. The non-transitory computer readable medium of claim 19, wherein: The maintenance prompt includes at least one of the following: a title, a customer complaint phrase, a reason phrase, and a correction phrase.

Images