System and method for fleet-level mapping of fault code locations

Abstract

A method (600) for machine fault location mapping, comprising: receiving fault event information (602) for machines (20) distributed within a geographic area; receiving location information (604) corresponding to the received fault event information; receiving severity information (606) corresponding to the received fault event information, wherein the severity information includes an indication of high, medium, or low severity; and presenting a graphical user interface (300) on a display device (108), wherein the graphical user interface (300) covers at least the geographic area The method (600) includes a map (302) representing a portion of the ring (330), and fault cluster indicators (310, 312, 314) located on the map (302) representing fault events that occurred on multiple machines (20) located within a selected cluster distance, wherein the fault cluster indicators (310, 312, 314) indicate the number of high-severity events (332) as a proportion of combined high and medium-severity events as corresponding portions of the ring (330), and the total number of fault events represented by the fault cluster indicators is shown at the center of the ring (330) (336).

Description

Technical Field

[0001] This patent application is directed to machine management, more specifically, mapping and clustering of machine fault code locations.

Background Art

[0002] Managing a fleet of machines such as excavators, bulldozers, and haul trucks can become difficult, specifically as the number of machines and job sites increases. For example, a fleet manager needs the ability to visualize which machines in the fleet are experiencing fault codes, what types of faults those machines are experiencing, and where those assets are located. Location data is provided when a fault code is reported, but fault codes have conventionally been provided in a list view with only address links. Additionally, some mapping capabilities for faults at the fleet level are provided to assist the fleet manager in determining how to respond to a particular fault. This can be useful in identifying problem assets, but the fleet manager cannot easily understand why the faults are occurring.

[0003] Efforts have been made to provide fleet visualization methods. For example, U.S. Patent No. 10,515,492 to Mattern et al. (hereinafter, "Mattern") describes a data visualization method, where an aggregation circuit is structured to receive at least one of (i) vehicle data indicating at least one operating characteristic of one or more vehicles from one or more vehicles, and (ii) technician data indicating at least one diagnostic characteristic of one or more vehicles representing technician service events. A data visualization circuit is structured to receive a display request for providing a graphical user interface to a user display device. The display request includes configurable options for providing the graphical user interface in a desired graphical format including at least one of the vehicle data and the technician data.

[0004] Furthermore, Folken et al., U.S. Patent Application Publication No. 2016 / 0117059 (hereinafter, "Folken"), describes a user interface for a fleet management web portal for manufacturers, operators, or users to manage a fleet of equipment and / or machinery. A fleet of equipment and / or machinery may be linked to the fleet management web portal, and manufacturers, operators, or users may use electronic devices to access alarms and other information associated with the equipment and / or machinery. The user interface is compatible with electronic devices of various sizes and allows users to interact with information associated with a fleet of equipment and / or machinery. Mattern and Folken provide fault code information and mapping capabilities, but do not provide context about fault codes that could help a fleet manager determine the cause of those faults and the appropriate response.

[0005] Therefore, there is still an opportunity to improve the fleet-level mapping of failure codes, which would help provide insights into the potential causes of those failures. The exemplary systems and methods described herein are intended to overcome one or more of the aforementioned defects and / or other problems in the prior art. [Overview of the Initiative]

[0006] In some embodiments, the technology described herein relates to a method for machine fault location mapping, the method comprising: receiving fault event information for a plurality of machines distributed within a selected geographical area; receiving location information corresponding to the received fault event information; receiving severity information corresponding to the received fault event information, wherein the severity information includes an indication of high, medium, or low severity; and presenting a graphical user interface on a display device, the graphical user interface comprising: a map representing at least a portion of the geographical area; and at least one fault cluster indicator located on the map representing fault events occurring on a plurality of machines located within a selected cluster distance, the fault cluster indicator indicating the number of high-severity events as a proportion of combined high and medium-severity events as a corresponding portion of a ring, and the total number of fault events represented by the fault cluster indicator being numerically indicated at the center of the ring.

[0007] In some embodiments, the techniques described herein relate to methods, wherein the graphical user interface further includes at least one fault marker located outside a selected cluster distance, the fault marker including a severity indicator.

[0008] In some embodiments, the techniques described herein relate to a method, the method further comprising receiving a selection of at least one fault marker and, in response to receiving a selection of at least one fault marker, displaying corresponding fault information overlaid on a map.

[0009] In some embodiments, the techniques described herein relate to methods, and the failure information includes a machine identifier, a total number of machine hours, and a failure code.

[0010] In some embodiments, the techniques described herein relate to methods, and the graphical user interface further includes a list of each fault event currently displayed on the map.

[0011] In some embodiments, the techniques described herein relate to methods in which fault event information, location information, and severity information are received from a corresponding one of a group of machines.

[0012] In some embodiments, the techniques described herein relate to methods, where failure event information corresponds to failures observed during a selectable period.

[0013] In some embodiments, the technology described herein relates to a machine fault location mapping system, which includes one or more processors and one or more memory devices storing instructions, wherein when an instruction is executed by one or more processors, it causes one or more processors to receive fault event information for a plurality of machines distributed within a selected geographical area, to receive location information indicating the location where one or more of the fault events occurred, to receive severity information for one or more fault events, wherein the severity information includes an indication of high, medium, or low severity, and to present a graphical user interface on a display device, the graphical user interface includes a map representing at least a portion of the geographical area and at least one fault cluster indicator located on the map representing fault events that occurred on a plurality of machines located within a selected cluster distance, the fault cluster indicator showing the number of high-severity events as a proportion of combined high and medium-severity events as a corresponding portion of a ring, and the total number of fault events represented by the fault cluster indicator is numerically shown at the center of the ring.

[0014] In some embodiments, the technology described herein relates to a system, the graphical user interface further includes at least one fault marker located outside a selected cluster distance, the fault marker includes a severity indicator.

[0015] In some embodiments, the techniques described herein relate to a system, which further includes receiving a selection of at least one fault marker and, in response to receiving a selection of at least one fault marker, displaying corresponding fault information overlaid on a map.

[0016] In some embodiments, the technology described herein relates to a system, and the fault information includes a machine identifier, a total number of machine hours, and a fault code.

[0017] In some embodiments, the technology described herein relates to a system, the graphical user interface further includes a list of each fault event currently displayed on the map.

[0018] In some embodiments, the technology described herein relates to a system in which fault information, location information, and severity information are received from a corresponding one of a group of machines.

[0019] In some embodiments, the technology described herein relates to a system in which failure event information corresponds to failures observed during a selectable period.

[0020] In some embodiments, the technology described herein relates to one or more non-temporary computer-readable media storing computer executable instructions, wherein when the computer executable instructions are executed by one or more processors, the one or more processors perform an operation that includes receiving fault event information for a plurality of machines distributed within a selected geographical area, receiving location information indicating that one or more of the fault events have occurred, receiving severity information for one or more fault events, wherein the severity information includes an indication of high, medium, or low severity, and presenting a graphical user interface on a display device, the graphical user interface including a map representing at least a portion of the geographical area, and at least one fault cluster indicator located on the map representing fault events that have occurred on a plurality of machines located within a selected cluster distance, the fault cluster indicator indicating the number of high-severity events as a proportion of combined high and medium-severity events as a corresponding portion of a ring, and the total number of fault events represented by the fault cluster indicator is numerically indicated at the center of the ring.

[0021] In some embodiments, the technology described herein relates to a non-transient computer-readable medium, wherein the graphical user interface further includes at least one fault marker located outside a selected cluster distance, the fault marker including a severity indicator.

[0022] In some embodiments, the technology described herein relates to a non-temporary computer-readable medium, which further includes receiving a selection of at least one fault marker and, in response to receiving a selection of at least one fault marker, displaying corresponding fault information overlaid on a map.

[0023] In some embodiments, the technology described herein relates to a non-temporary computer-readable medium, and the fault information includes a machine identification, machine time, and fault code.

[0024] In some embodiments, the technology described herein relates to a non - transient computer - readable medium, and the graphical user interface further includes a list of each obstacle event currently displayed on the map.

[0025] In some embodiments, the technology described herein relates to a non - transient computer - readable medium, and the obstacle event information, location information, and severity information are received from a corresponding one of a plurality of machines. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The systems and methods described herein may be better understood by reference to the following detailed description taken in conjunction with the accompanying drawings, in which like reference numerals identify identical or functionally similar elements.

[0027] [Figure 1] FIG. 1 shows an overview of an environment in which a partial implementation of a fleet - level fault code mapping system according to some embodiments of the disclosed technology can operate. [Figure 2] FIG. 2 is a diagram of a graphical user interface for machine usage visualization according to some embodiments of the disclosed technology. [Figure 3] FIG. 3 is an enlarged view of a portion of the graphical user interface for machine usage visualization. [Figure 4] FIG. 4 is an enlarged view of the graphical user interface for machine usage visualization. [Figure 5] FIG. 5 is an enlarged view of the fault cluster indicator shown in FIGS. 3 and 4 according to some embodiments of the disclosed technology. [Figure 6] FIG. 6 is a flowchart showing a method for fleet - level fault code mapping according to some embodiments of the disclosed technology. [Figure 7] FIG. 7 is a block diagram showing an overview of a device in which some implementations can operate. [Figure 8] FIG. 8 is a block diagram showing an overview of an environment in which some implementations can operate. [Figure 9] This is a block diagram showing components that can be used in systems employing the disclosed technology in certain implementation forms.

[0028] The headings provided herein are for convenience only and do not necessarily affect the scope of the embodiments. Furthermore, the drawings are not necessarily to exact scale. For example, the dimensions of some elements in the drawings may be enlarged or reduced to help improve the understanding of the embodiments. Moreover, while the disclosed art is suitable for various modifications and alternative forms, specific embodiments are illustrated in the drawings and described in detail below. However, this is not intended to unnecessarily limit the embodiments described. Rather, the embodiments are intended to cover all suitable modifications, combinations, equivalents, and alternatives that fall within the scope of this disclosure. [Modes for carrying out the invention]

[0029] Herein, various embodiments of the systems and methods described above will be described in more detail. The following description provides specific details to enable a full understanding and explanation of these embodiments. However, those skilled in the art will understand that the techniques and technologies discussed herein can be practiced without many of these details. Similarly, those skilled in the art will understand that the technology may include many other features not described in detail herein. In addition, some known structures or functions may not be shown or described below in detail to avoid unnecessarily obscuring the relevant description.

[0030] The terms used below are used in conjunction with the detailed descriptions of certain embodiments of some of the embodiments, but are to be interpreted in their most reasonably broad sense. In fact, some terms may be emphasized below, but any term intended to be interpreted in any restricted form is so explicitly and specifically defined in this section.

[0031] Fleet managers need the ability to visualize where fault codes are occurring at the fleet level. While location data is provided when fault codes are reported, fault codes have traditionally only been provided in a list view with address links. Additionally, the ability to map faults at the fleet level is limited to the asset level rather than the fault level, and is displayed by the location of the asset rather than the location of the fault itself. While this may be useful for identifying problematic assets, fleet managers cannot easily understand where faults are circumstantial, and therefore cannot assess and address geographical trends.

[0032] The disclosed technology provides a fleet-level mapping of fault code locations. Rather than placing indicators (e.g., pins) at the reported locations of assets and providing supplemental fault code information, the system provides a fault code location display that focuses on the fault itself. In other words, the location of the pins on the map is based on the specific geographic location where the fault occurred, regardless of the asset's current location. Each pin provides fault code information: severity, description, source, date, time, and location, as well as information about the asset reporting the fault (asset ID / SN, manufacturer, model, time, and odometer, and current status and last reported location). This allows fleet managers to understand faults in the context of where they occurred. Additionally, the map clusters faults that occur in the same geographic area. This allows fleet managers to assess geographic-based trends, address problem areas within the work area, and identify operator training opportunities based on the types of fault codes that are frequently triggered at the same locations.

[0033] Figure 1 shows an environment 10 in which some implementations of the fault code mapping system 100 according to the disclosed embodiment of the technology can operate. The system environment 10 may include several machines such as excavators 20(1) and 20(2), a satellite 12, a telematics / utilization database 102, a fault code database 104, a telematics processing system 106, a display 108, and a network 110. The fault code mapping system 100 may connect to the telematics / utilization database 102, the fault code database 104, the telematics processing system 106, and the display 108 via the network 110. The telematics / utilization database 102, the fault code database 104, and the telematics processing system 106 may receive fault codes and telematics data from the excavators 20(1) and 20(2) via the satellite 12. The telematics data may include machine operating time, idle time, and machine identification information, such as type and model number. Telematics data can also include sensor data from the excavator, such as pressure sensor 22, vibration sensor 24, and temperature sensor 26, to name a few.

[0034] In some embodiments, the telematics processing system 106 determines machine utilization patterns for a machine based on telematics data. For example, a machine learning model (such as a neural network) can be applied to estimate the utilization pattern of each machine based on telematics data (i.e., telemetry data). In one embodiment, an excavator may have an activity utilization pattern that includes, for example, 50% heavy excavation, 20% leveling, and 30% tracking (i.e., movement from place to place). In some embodiments, the utilization model can be a mathematical model that classifies machine activity or application frequency, which may include regression, support vector machines, and neural networks, depending on the required level of detail and complexity. These models may distinguish between, for example, heavy excavation, dust movement, trenching, scraping, leveling, loading, tracking, or idle time. The model may be supplemented with standard telematics data with additional sensors to measure utilization intensity. In some embodiments, the resulting machine utilization pattern, or activity data, can be provided to the fault code mapping system 100, in addition to run time, idle time, fault codes, and machine identification information.

[0035] The fault code mapping system 100 can be configured to receive fault event information, location information, and fault severity information for multiple machines distributed within a selected geographical area, either from the machines themselves or via one or more databases such as the telematics / utilization database 102 and / or the fault code database 104. The fault code mapping system 100 can cluster fault code events based, for example, on fault type, severity, and geographical location. The system 100 can then present a graphical user interface (GUI) on a display device 108 for review by a user, such as a fleet manager.

[0036] Referring to Figure 2, the fault code mapping system 100 is configured to output a graphical user interface (GUI) 200 to a suitable display device such as a display device 108 (Figure 1). As shown in the figure, a map 202 representing at least a portion of a geographical area is presented on the GUI 200. The system clusters fault events that have occurred on multiple machines at locations within a selected cluster distance. At least one fault cluster indicator 210 is positioned on the map 202 representing the clustered faults. As will be described in more detail below with respect to Figure 5, the indicator 210 can indicate the number of faults in the cluster, as well as the severity of the faults. In some embodiments, a data range 204 can be selected. Thus, the displayed fault event information (i.e., the fault cluster indicator 210) corresponds to faults observed during the selected period. In addition to the map portion 202, the GUI 200 may also include a list portion 206 for each fault event currently displayed on the map, along with machine identification and the location where the fault occurred.

[0037] Figure 3 shows another embodiment of GUI 300, including a map 302 having multiple fault cluster indicators 310, 312, and 314. The fault cluster indicators located on the map represent fault events that occurred on multiple machines located within a selected cluster distance (e.g., a diameter of 20 miles) of the indicator, and the indicators are centered relative to the fault event locations. Similar to GUI 200 described above, GUI 300 may include a list section 306 containing fault information 320. GUI 300 may also include service locations such as location 318 and fault markers such as marker 316.

[0038] Referring further to Figure 4, as described above, the GUI 300 may include fault markers, such as marker 316, that are located outside the range (e.g., distance) of each fault cluster indicator. For example, fault marker 316 is outside the range of the selected distance corresponding to fault cluster indicator 312. When fault marker indicator 316 is selected or the mouse is moved over it, the system displays the corresponding fault information, for example, overlaid on the map in a pop-up window 322. In some embodiments, fault markers may include severity indicators in the form of text and / or color-coded dots, as shown.

[0039] As shown in Figure 5, in some embodiments, each fault cluster indicator, such as indicator 312, indicates the number of high-severity events as a combined percentage of high and medium-severity events as corresponding parts of the ring 330. For example, in the embodiment shown, part 332 is the high-severity portion, and part 334 is the medium-severity portion. The total number of fault events 336 represented by the fault cluster indicator is numerically displayed in the center of the ring 330. In some embodiments, different parts of the ring can be color-coded. In some embodiments, when a user selects or moves the mouse over a fault cluster indicator 312, a pop-up window may appear displaying, for example, the date, the percentage of high-severity events, the percentage of medium-severity events, and the location. In some embodiments, the fault cluster indicator may include a pie chart, a bar chart divided into high and medium severity levels, or other preferred graphical arrangements. The fault cluster indicator provides an efficient way for users to quickly compare performance between similar machines in the work area and identify problems. This condensed display arrangement also provides the user with tools to drill down to identify potential causes of fault codes and how to correct them. In some embodiments, by selecting a fault cluster indicator, the system zooms in on the map, breaking down individual fault events and smaller clusters.

[0040] Figure 6 is a flowchart showing a method 600 for machine fault code location mapping according to some embodiments of the disclosed technology. Method 600 may include receiving fault event information for a plurality of machines distributed within a selected geographical area in step 602. In step 604, location information corresponding to the received fault event information is received. The location information may indicate the location where the corresponding fault event occurred. In step 606, severity information is received for the corresponding fault event. The severity information may include an indication of high, medium, or low severity. A graphical user interface (GUI) is presented on a display device in step 608. In step 610, a map representing at least a portion of the geographical area is presented on the GUI. In step 612, the system clusters fault events that occurred on a plurality of machines located within a selected cluster distance. At least one fault cluster indicator is positioned on the map representing the clustered faults in step 614. In some embodiments, the fault cluster indicator shows the number of high-severity events as a proportion of combined high and medium-severity events in a corresponding portion of a ring, and the total number of fault events represented by the fault cluster indicator is numerically shown in the center of the ring.

[0041] In some embodiments, the graphical user interface further comprises at least one fault marker located outside a selected cluster distance, the fault marker including a severity indicator. Method 600 may also include receiving a selection of at least one fault marker and, in response, displaying corresponding fault information overlaid on the map. The fault information may include, for example, a machine identification, a total number of machine hours, and a fault code. In some embodiments, the graphical user interface may further comprise a list of each fault event currently displayed on the map. Fault event information, location information, and severity information may be received from a corresponding one of a plurality of machines. The fault event information may correspond to faults observed during a selectable period.

[0042] In some embodiments, the disclosed systems and methods can automatically flag high-occurrence fault codes. The system can determine fault codes with multiple occurrences and filter the most frequent fault codes. The high-occurrence fault codes can then be displayed and clustered to provide fleet manager context for multiple occurrences. For example, all faults may occur near a particular work site or geographical feature and / or under local weather conditions (e.g., rain). All of these may have bearings regarding the reason for the faults occurring. For example, an overspeed fault may be a result of a particular hill (i.e., a geographical feature) at the work site. A suitable solution might be to change the slope of the hill or change the machine's route to avoid the hill. In another embodiment, a wheel slip fault (indicating tire wear) may be a result of reduced traction due to rain (i.e., weather conditions) at a particular location. Faults that may be related to a work site may include the duration of time at that site, temperature conditions, driver training level, etc. Therefore, the system can automatically flag and provide context for high-occurrence fault codes to help the fleet manager diagnose and take appropriate action.

[0043] Suitable system The technologies disclosed herein can be embodied as dedicated hardware (e.g., circuits), as programmable circuits appropriately programmed with software and / or firmware, or as a combination of dedicated and programmable circuits. Accordingly, embodiments may include machine-readable media having stored instructions that can be used to cause a computer, microprocessor, processor, and / or microcontroller (or other electronic device) to carry out a process. Machine-readable media may include, but are not limited to, optical discs, compact disc read-only memory (CD-ROM), magneto-optical discs, ROMs, random access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic or optical cards, flash memory, or other types of media / machine-readable media suitable for storing electronic instructions.

[0044] Some implementations will be discussed in more detail below with reference to the figures. Figure 7 is a block diagram illustrating an overview of a device in which some implementations of the disclosed technology can operate. The device may comprise, for example, the hardware components of device 700. Device 700 may include one or more input devices 720 that provide input to a CPU (processor) 710 to notify it of an action. The action is typically mediated by a hardware control device that interprets signals received from the input devices and communicates the information to the CPU 710 using a communication protocol. The input devices 720 include, for example, a mouse, keyboard, touchscreen, infrared sensor, touchpad, wearable input device, camera or image-based input device, microphone, or other user input device.

[0045] The CPU 710 can be a single processing unit or multiple processing units within a device, or it can be distributed across multiple devices. The CPU 710 can be coupled to other hardware devices using a bus, such as a PCI bus or SCSI bus. The CPU 710 can communicate with hardware control devices for devices such as the display 730. The display 730 can be used to display text and graphics. In some embodiments, the display 730 provides graphical and textual visual feedback to the user. In some implementations, the display 730 includes the input device as part of the display, such as when the input device is a touchscreen or equipped with an eye-direction monitoring system. In some implementations, the display is separate from the input device. Examples of display devices include LCD screens, LED screens, projection displays, holographic displays, or augmented reality displays (such as head-up display devices or head-mounted devices). Other I / O devices 740 can also be coupled to the processor, such as network cards, video cards, audio cards, USB, FireWire or other external devices, sensors, cameras, printers, speakers, CD-ROM drives, DVD drives, disc drives, or Blu-ray devices.

[0046] In some implementations, device 700 also includes a communication device that can communicate with network nodes wirelessly or via a wired connection. The communication device can communicate with another device or server over the network, for example, using the TCP / IP protocol. Device 700 can utilize the communication device to distribute operations across multiple network devices.

[0047] The CPU 710 may have access to memory 750. Memory includes one or more hardware devices for volatile and non-volatile storage devices and can include both read-only and writable memory. For example, memory can include random access memory (RAM), CPU registers, read-only memory (ROM), and writable non-volatile memory such as flash memory, hard drives, floppy disks, CDs, DVDs, magnetic storage devices, tape drives, and device buffers. Memory is not a propagating signal decoupled from the underlying hardware, and therefore memory is non-transient. Memory 750 may include program memory 760 that stores programs and software such as the operating system 762, the fault code mapping platform 764, and other application programs 766. Memory 750 may also include data memory 770, which may include database information that can be provided to program memory 760 or any element of device 700.

[0048] Some implementations may be operable in a number of other general-purpose or dedicated computing system environments or configurations. Examples of known computing systems, environments, and / or configurations that may be suitable for use with this technology include, but are not limited to, distributed computing environments that include any of the following: personal computers, server computers, handheld or laptop computers, mobile phones, mobile phones, wearable electronic devices, game consoles, tablet devices, microprocessor systems, microprocessor-based systems, programmable consumer electronics, network PCs, microcomputers, mainframe computers, and the systems or devices mentioned above.

[0049] Figure 8 is a block diagram illustrating an overview of an environment 800 in which some implementations of the disclosed technology can operate. The environment 800 may include one or more client computing devices 805A-D, and its embodiments may include device 700. A client computing device 805 may operate in a network environment using a logical connection to one or more remote computers, such as a server computing device 810, via a network 830.

[0050] In some implementations, server computing device 810 can be an edge server that receives client requests and coordinates the execution of those requests through other servers such as servers 820A-C. Server computing devices 810 and 820 can include computing systems such as device 700. Although each server computing device 810 and 820 is logically represented as a single server, each server computing device can be a distributed computing environment encompassing multiple computing devices located in the same or geographically different physical locations. In some implementations, each server computing device 820 corresponds to a group of servers.

[0051] Client computing device 805 and server computing devices 810 and 820 may each act as a server or client to other server / client devices. Server 810 can connect to database 815. Servers 820A to C can each connect to their corresponding databases 825A to C. As described above, each server 820 may correspond to a group of servers, each of which may share a database or have its own database. Databases 815 and 825 can store (e.g., store) information. Although databases 815 and 825 are logically represented as a single unit, each database 815 and 825 can be a distributed computing environment encompassing multiple computing devices, located within their corresponding servers, or located in the same or geographically different physical locations.

[0052] Network 830 may be a local area network (LAN) or a wide area network (WAN), but it may also be any other wired or wireless network. Network 830 may be the Internet or any other public or private network. Client computing devices 805 may connect to network 830 via a network interface, such as by wired or wireless connection. Although the connection between server 810 and server 820 is shown as a separate connection, these connections may be any kind of local, wide area, wired, or wireless network, including network 830 or any other public or private network.

[0053] Figure 9 is a block diagram showing components 900 that can be used in a system using the disclosed technology in some implementation forms. Component 900 includes hardware 902, general-purpose software 920, and dedicated components 940. As described above, a system implementing the disclosed technology can use various hardware, including a processing unit 904 (e.g., CPU, GPU, APU, etc.), working memory 906, storage memory 908, and input and output devices 910. Component 900 can be implemented on a client computing device such as a client computing device 805, or on a server computing device such as a server computing device 810 or 820.

[0054] The general-purpose software 920 may include a variety of applications, including an operating system 922, a local program 924, and a basic input / output system (BIOS) 926. Dedicated components 940 may be sub-components of the general-purpose software application 920, such as the local program 924. Specialized components 940 may include a data acquisition module 944, a graphics module 946, a geolocation module 948, a telematics / utilization module 950, and components that transfer data and may be used to control dedicated components such as the interface 942. In some implementations, components 900 may reside in a computing system distributed across multiple computing devices, or they may interface to a server-based application running one or more of the dedicated components 940.

[0055] Those skilled in the art will understand that each of the components shown in Figures 7 to 9 and the flowcharts described above can be modified in various ways. For example, the order of logic can be rearranged, substeps can be performed in parallel, illustrated logic can be omitted, and other logic can be included. In some implementations, one or more of the above components can perform one or more of the processes described herein. [Industrial applicability]

[0056] In some embodiments, the fault code mapping system may include a data acquisition module 944, a graphics module 946, a geolocation module 948, and a telematics / utilization module 950 (Figure 9). During operation, the data acquisition module 944 may receive telematics data from the telematics / utilization module 950, for example, fault codes and severity levels. The telematics / utilization module 950 may receive and process telematics data from various machines such as trucks, bulldozers, and excavators. The telematics data may include machine uptime, idle time, fault codes, and machine identification information, for example, type and model number. In some embodiments, the geolocation module 948 may determine and provide fault event location information to the data acquisition module 944. In some embodiments, the data acquisition module 944 may receive fault event location and severity information from a different domain or database, in addition to or instead of the geolocation module 948. The data acquisition module 944 combines all the data and provides it to the graphics module 946, which outputs a GUI for presentation on a display device, including fault cluster indicators.

[0057] remarks The above description and drawings are illustrative and should not be construed as limiting. Numerous specific details are described in order to provide a complete understanding of this disclosure. However, in some cases, known details are omitted to avoid obscuring the description. Furthermore, various modifications can be made without departing from the scope of the embodiments.

[0058] Any reference in this specification to “one embodiment” or “embodiment” means that certain features, structures, or characteristics described in relation to an embodiment are included in at least one embodiment of this disclosure. The phrase “in one embodiment” appearing in various parts of this specification does not necessarily refer to the same embodiment, nor does it imply separate or alternative embodiments that exclude each other. Furthermore, various features that may be shown in some embodiments but not in others are described. Similarly, various requirements that may be necessary in some embodiments but not in others are described.

[0059] The terms used herein generally have their usual meanings in the art, within the context of the disclosure, and in the specific context in which each term is used. It will be understood that the same can be said in multiple ways. Therefore, alternative expressions and synonyms may be used for any one or more of the terms discussed herein, and there is no particular importance in whether or not a term is elaborated upon or discussed herein. Synonyms are provided for some terms. The explanation of one or more synonyms does not preclude the use of other synonyms. The use of examples anywhere in this specification, including examples of any term discussed herein, is illustrative only and is not intended to further limit the scope and meaning of this disclosure or the scope and meaning of any exemplary term. Similarly, this disclosure is not limited to the various embodiments given herein. Unless otherwise defined, all technical and scientific terms used herein have the same meanings as commonly understood by those skilled in the art to whom this disclosure relates. In case of any conflict, this specification, including definitions, shall prevail.

Claims

1. A method for mapping the location of a machine fault (600), wherein the method is Receiving fault event information (602) for multiple machines (20) distributed within a selected geographical area, Receiving location information corresponding to the received fault event information (604), Receiving severity information corresponding to the received fault event information, wherein the severity information includes an indication of high, medium, or low severity (606), The method includes presenting a graphical user interface (300) on a display device (108) (608), wherein the graphical user interface (300) is A map (302) representing at least a portion of the aforementioned geographical area, The system comprises at least one fault cluster indicator (310, 312, 314) located on the map (302) that represents fault events occurring on the plurality of machines (20) located within a selected cluster distance, Method (600), wherein the fault cluster indicators (310, 312, 314) indicate the number of high-severity events (332) as a proportion of combined high and medium-severity events as corresponding parts of the ring (330), and the total number of fault events represented by the fault cluster indicators is numerically shown at the center of the ring (330) (336).

2. The method according to claim 1 (600), wherein the graphical user interface (300) further comprises at least one fault marker (316) located outside the selected cluster distance, and the fault marker (316) includes a severity indicator.

3. The method according to claim 2 (600), further comprising receiving the selection of at least one fault marker (316), and displaying corresponding fault information (322) overlaid on the map in response to receiving the selection of at least one fault marker.

4. The method according to claim 3 (600), wherein the fault information (322) includes a machine identifier, a total number of machine hours, and a fault code.

5. The method according to claim 1 (600), wherein the graphical user interface (300) further includes a list (306) of each fault event (320) currently displayed on the map (302).

6. The method according to claim 1 (600), wherein the fault event information (322), the location information, and the severity information are received from a corresponding one of the plurality of machines (20).

7. The method according to claim 1 (600), wherein the fault event information (322) corresponds to a fault observed during a selectable period.

8. A machine fault location mapping system (100), One or more processors (710), The system comprises one or more memory devices (750) in which instructions are stored, and when an instruction is executed by the one or more processors (710), the one or more processors (710) receive instructions. The system receives fault information (602) about multiple machines (20) distributed within a selected geographical area. The system receives location information indicating the location where one or more of the aforementioned failure events occurred (604), Severity information for one or more of the aforementioned failure events, wherein the severity information includes an indication of high, medium, or low severity, is received (606). A graphical user interface (300) is displayed on a display device (108) (602), and the graphical user interface (300) is, A map (302) representing at least a portion of the aforementioned geographical area, The system comprises at least one fault cluster indicator (310, 312, 314) located on the map (302) that represents fault events occurring on the plurality of machines (20) located within a selected cluster distance, System (100), wherein the fault cluster indicators (310, 312, 314) indicate the number of high-severity events (332) as a proportion of combined high and medium-severity events in the corresponding portion of the ring (330), and the total number of fault events represented by the fault cluster indicators is numerically indicated (336) at the center of the ring (330).

9. The system (100) according to claim 8, wherein the graphical user interface (300) further comprises at least one fault marker (316) located outside the selected cluster distance, and the fault marker (316) includes a severity indicator.

10. The system (100) according to claim 9, further comprising receiving the selection of at least one fault marker (316), and displaying corresponding fault information (322) overlaid on the map (302) in response to receiving the selection of at least one fault marker (316).

Images