METHOD AND SYSTEM TO ASCERTAIN A REPAIR FOR AN ASSET

Abstract

Systems and methods of the invention relate to indicating a repair to perform on an asset based on historic data related to a repair on the asset and/or sensor data associated with the asset. An evaluate component aggregates information related an asset such as a repair performed or data from a sensor. A repair evaluation component indicates a repair to perform on the asset based on at least one of the data from the sensor or the information related to the asset. By utilizing asset-specific information and historical data, repair schedules for assets can be more accurate and thereby reducing untimely repairs.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Ser. No. 61/704,691, filed Sep. 24, 2012, and entitled “VEHICLE REPAIR SYSTEMS AND METHODS.” The entirety of the aforementioned application is incorporated herein by reference.

BACKGROUND

1. Technical Field

Embodiments of the subject matter disclosed herein relate to identifying a repair or maintenance for one or more assets.

2. Discussion of Art

Maintenance performed on assets and/or vehicles can prolong asset-life and minimize downtime thereof. Conventional techniques often include preventative maintenance to be employed on assets/vehicles, wherein such maintenance is performed based on a manufacturer suggestion (e.g., mileage, duration of time, among others). Yet, each asset or vehicle may require a maintenance before or after the manufacturer suggestion in light of, for instance, the amount of use, type of use, environment, among others for the vehicle or asset. For instance, a manufacturer may suggest a duration of time as a trigger for a maintenance procedure but this duration of time may be short (e.g., thus performing the maintenance too soon and increasing cost) or long (e.g., thus performing the maintenance too late and increasing risk for damage).

It may be desirable to have a system and method that differs from those systems and methods that are currently available.

BRIEF DESCRIPTION

In an embodiment, a method is provided that includes at least the steps of: evaluating, with at least one component, a portion of sensor data related to an asset; evaluating, with the at least one component, a portion of historic data associated with at least one historic repair to the asset; and indicating, with the at least one component, a future repair to perform on the asset based on at least one of the portion of sensor data or the portion of historic data.

In an embodiment, a system is provided that includes a first component configured to collect at least one of a portion of sensor data related to an asset or a portion of historic data related to a historic repair performed on the asset. The system can include a second component configured to identify an indicator to perform a future repair on two or more assets based on at least one of the portion of sensor data collected by the first component or the portion of historic data collected by the first component.

In an embodiment, a system can be provided that includes means for evaluating a portion of sensor data related to an asset. The system can include means for evaluating a portion of historic data associated with a repair to the asset. The system can include means for indicating a repair to perform on the asset based on at least one of the portion of sensor data or the portion of historic data.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference is made to the accompanying drawings in which particular embodiments and further benefits of the invention are illustrated as described in more detail in the description below, in which:

FIG. 1 is an illustration of an embodiment of a system for ascertaining a repair to perform on an asset based on at least one of repair information or sensor data;

FIG. 2 is an illustration of an embodiment of a system for utilizing historic data related to a repair on an asset and sensor data for the asset to indicate a repair to perform on the asset at a particular date or time;

FIG. 3 is an illustration of an embodiment of a system for creating an indicator for an asset which determines a timing for a repair to perform on at least the asset or an additional asset;

FIG. 4 is an illustration of an embodiment of a system for ascertaining a cost associated with a repair to perform on an asset; and

FIG. 5 illustrates a flow chart of an embodiment of a method for identifying a repair to perform on an asset.

DETAILED DESCRIPTION

Embodiments of the invention relate to methods and systems for indicating a repair to perform on an asset based on historic data related to a repair on the asset and/or sensor data associated with the asset. An evaluate component aggregates information related an asset such as a repair performed or data from a sensor. A repair evaluation component indicates a repair to perform on the asset based on at least one of the data from the sensor or the information related to the asset. By utilizing asset-specific information and historical data, repair schedules for assets can be more accurate and thereby reducing untimely repairs.

With reference to the drawings, like reference numerals designate identical or corresponding parts throughout the several views. However, the inclusion of like elements in different views does not mean a given embodiment necessarily includes such elements or that all embodiments of the invention include such elements.

The term “component” as used herein can be defined as a portion of hardware, a portion of software, or a combination thereof. “Hardware” refers to electronic circuits/circuitry, logic circuits/circuitry, and/or one or more processing elements (e.g., microprocessors or controllers) that is configured for the carrying out of one or more functions and/or methods (e.g., functions and/or methods as set forth herein), through execution of associated software (stored in a non-transitory electronic-readable medium, which may be part of the hardware), through the arrangement of the circuits/circuitry, and/or otherwise. “Software” refers to instructions that are readable and/or executable by hardware, stored in non-transitory electronic-readable media, which cause the hardware to perform designated functions, designated actions, and/or behave in a desired manner. “Non-transitory electronic-readable media” include, but are not limited to, non-volatile RAM, ROM, PROM, etc., a CD-ROM, a removable flash memory card, a hard disk drive, a magnetic tape, a floppy disk, and/or combinations thereof. The term “client asset” or “asset” as used herein means a fixed asset or a mobile asset that is owned and/or operated by a client entity such as, for example, a railroad, a power generation company, a shipping company (e.g., land, sea, air, and/or an combination thereof), a mining equipment company, an airline, or another asset-owning and/or asset-operating entity. The term “vehicle” as used herein can be defined as an asset that is a mobile machine or a moveable transportation asset that transports at least one of a person, people, or a cargo. For instance, a vehicle can be, but is not limited to being, a rail car, an intermodal container, a locomotive, a marine vessel, mining equipment, a stationary power generation equipment, industrial equipment, construction equipment, and the like. The term “repair facility” as used herein can be defined as a location that evaluates and/or performs a repair on a vehicle or other client asset. The term “Car Repair Billing” (CRB) as used herein can be defined as a computer-implemented system with a portion of software, a portion of hardware, or a combination thereof that facilitates reporting and/or auditing railroads, car owners, client asset owners, vehicle owners, lessee, lessor, among others. CRB includes Association of American Railroads (AAR) administered as well as contract billing, and another suitable billing for railroads.

The term “Maintenance Management System” (MMS) as used herein can be defined as a computer-implemented system with a portion of software, a portion of hardware, or a combination thereof that facilitates analyzing repairs for a vehicle and/or auditing repairs for a vehicle to railroads, car owners, client asset owners, vehicle owners, lessee, lessor, among others. The MMS can receive repair information from a repair facility. The vehicle owner can use MMS to input repair data received from repair facility and then views, audits, pays, etc. based on the data received. The term “part” as used herein can be defined as a portion of a client asset and/or a portion of a vehicle, wherein the “part” is involved in a repair for at least one of the client asset or the vehicle. The term “ownership” as used herein can be defined as proof of legal claim to property such as a vehicle. The proof can be a title, a lease agreement, a contract, a legal document, a purchase agreement, among others. The term “repair” as used herein can be defined as a service on a vehicle, wherein the service can be a repair of a part, a replacement of a part, a maintenance of a part, a repair of a portion of the vehicle, a replacement of a portion of the vehicle, a maintenance of a portion of the vehicle, and the like. The term “substantially similar” as used herein can be defined as exactly the same, similar to one another in that more than half of one element is the same as another element. In another embodiment, “substantially similar” a first element can be 75% the same as a second element.

FIG. 1 is an illustration of a system 100 for ascertaining a repair to perform on an asset based on at least one of repair information (e.g., also referred to as a portion of historic data) or sensor data (also referred to as a portion of sensor data). The system 100 includes an evaluate component 110 that can be configured to aggregate (e.g., collect, retrieve, request and receive, among others) or receive at least one of a repair information or sensor data related to an asset. Repair information utilized by the system can include a portion of historic data related to an asset or a repair on the asset (described below). The system can include a repair evaluation component 120 can be configured to indicate a repair to perform on the asset based at least in part upon the repair information or the sensor data. By way of example and not limitation, the repair to perform on the asset can be performed at a later point in time in comparison to a repair the repair data is associated with (e.g., the repair information evaluated, the sensor data evaluated, among others). In an embodiment, the repair evaluation component can generate an indicator for a repair on an asset, wherein the indicator is based at least in part upon the portion of historic data related to the repair on the asset or the portion of sensor data related to the asset.

In one embodiment, an asset can include a repair such as an oil change in which a manufacturer suggested indicator can be a first mileage. The asset can include a user-defined indicator to perform the oil change such as a second mileage. Yet, based on the evaluation of historic data related to the asset and/or the repair, and/or a portion of sensor data (e.g., oil integrity sensor, oil samples collected, among others), an indicator of a third mileage can be implemented in order to ascertain a repair to perform on the asset and a time or date to perform the repair. By evaluating each asset performance and conditions of use (e.g., discussed more below), a repair to perform can be indicated and an appropriate frequency to implement such repair can be used (e.g., utilizing a created indicator that includes a time or date to perform a repair on an asset).

The repair evaluation component can be configured to calculate a date or time associated with the indicated repair. For instance, the date or time can be a projected deadline in which the indicated repair should be performed in order to mitigate damage (e.g., part failure, asset failure, degradation of asset performance, increase risk of damage, among others) for the asset. The projected date or time can be based on the portion of historic data or the portion of sensor data in which an indicator can be created (referenced above).

The evaluate component can be a stand-alone component (as depicted), incorporated into the repair evaluation component, or a combination thereof. The repair evaluation component can be a stand-alone component (as depicted), incorporated into the evaluate component, or a combination thereof. Moreover, the system can be implemented within or part of at least one of a Software as a Service (SaaS), cloud-computing environment, a network environment, a local network, a remote network environment, or the Internet.

FIG. 2 is an illustration of a system 200 for utilizing historic data related to a repair on an asset and sensor data for the asset to indicate a repair to perform on the asset at a particular date or time. The system includes the evaluate component that utilizes at least one of repair information (e.g., also referred to as a portion of historic data related to a repair performed on an asset) or sensor data (e.g., also referred to as a portion of sensor data related to the asset). The repair evaluation component leverages the portion of historic data and/or the portion of sensor data (via the evaluate component) to indicate a repair to perform (e.g., in a future point in time) on at least one asset.

By way of example and not limitation, repair information can be a previous repair on an asset, a part used in a repair on an asset, a date or time a repair was performed on an asset, a manufacturer suggested indicated to perform a repair on an asset, a user-defined indicator to perform a repair on an asset, a repair facility that performed the repair on the asset, repair details (e.g., who performed repair, issues related to performing the repair, duration of time to complete repair, downtime for the asset that received the repair, among others), financial information related to the repair (e.g., cost of repair, cost of part(s) for repair, among others), asset information (e.g., type of asset, use of asset, cargo load of asset, location of asset, conditions of use for asset, owner of asset, pricing contract for repairs to the asset, among others), data related to Maintenance Management System (MMS), data related to Car Repair Billing (CRB), and the like.

For instance, a repair can be previously performed on an asset ten (10) times in the past year, wherein the historic data (e.g., data related to the repair performed on the asset for those ten times) and/or sensor data (e.g., data collected related to the part(s) or portions of the asset affected by the repair, can be evaluated. Based on such evaluation, a projected estimate in time (e.g., also referred to as an indicator) for a repair (e.g., the same repair, a similar repair, a repair including one or more similar part(s), among others) to be performed can be indicated by the repair evaluation component.

The system can be utilized with a suitable Car Repair Billing (CRB), a CRB database 210, Maintenance Management System (MMS), and/or a MMS database 220, as well as an environment (e.g., user, repair shop, company, entity, corporation, among others) that employs CRB and/or MMS. For instance, the CRB database and/or the MMS database can be utilized by the evaluate component 110 in order to ascertain at least one of a history of repair(s), repairs performed, manufacturer suggested indicator, user-defined indicator, duration of repair, frequency of repair, part(s) used for a repair on an asset, cost of a repair, brand specific life expectancy, part life expectancy, among others.

The system can include one or more sensors 230, such as, for instance, sensor₁ to sensor_N, where N is a positive integer. The sensors can collect information from an asset in real-time, statically, or stored and subsequently accessed (e.g., collected). In an embodiment, the sensors can be a detector that utilizes real-time data collection or detection, wherein the detection is related to an asset. (Thus, a real time sensor is one that outputs sensor data substantially concurrently with what is being sensed, and/or that outputs data sufficiently rapidly for the system to control the source of the data. “Substantially concurrently” means but for delays due to electronic operation of the sensor, e.g., 100 msec or less.)

By way of example and not limitation, a portion of sensor data can be information received or collected from at least one of a wheel input, a load detector, a hot bearing detector, a dragging equipment, a real time sensor, a wheel degrade sensor, a flat spot detector, or an equipment health data sensor, among others. Still, an asset sensor or asset detector may be chosen with sound engineering judgment without departing from the intended scope of coverage of the embodiments of the subject invention. The sensors can collect information that can be evaluated in order to identify at least one of a repair to perform, a degradation of a part, a condition of an asset, a condition of a part, a condition of a repair, among others.

FIG. 3 is an illustration of a system 300 for creating an indicator for an asset which determines timing for a repair to perform on at least the asset or an additional asset. The evaluate component can aggregate data related to an asset via at least one of repair information (e.g., historic data related to a repair performed on the asset, among others) or sensor data (e.g., data related to an asset or a part in which such data is collected by a sensor or detector). Based on such evaluation, the repair evaluation component can indicate a repair to perform on the asset or an additional asset.

The repair evaluation component can be configured to ascertain an indicator for a repair to perform based on the portion of historic data or the portion of sensor data, wherein the indicator relates to at least one of the asset or a part associated with the indicated repair to perform. An indicator can be used by the repair evaluation component to indicate a repair to perform on an asset. In an embodiment, the evaluate component can receive or collect a user-defined indicator (e.g., user-defined indicator to perform a repair on an asset). In another embodiment, the evaluate component can receive or collect a manufacturer suggested indicator (e.g., manufacturer of a part or an asset that defines an indicator for a repair to perform on said part or said asset).

By way of example and not limitation, the indicator can be a duration of use, a duration of time, a measurement of distance traveled for the asset, or a failure rate. The indicator created by the repair evaluation component (e.g., based on repair information and/or sensor data) can be utilized to notify and/or trigger a performance of a repair on two or more assets. In an embodiment, the repair evaluation component can adjust a manufacturer suggested indicator related to performance of a repair based on at least one of the portion of historic data or the portion of sensor data. In an embodiment, the repair evaluation component can modify at least one of a user-defined indicator for a repair on an asset, a manufacturer suggested indicator for the repair on the asset, or a combination thereof based on at least one of the portion of historic data or the portion of sensor data.

The system can include a model component that can be configured to generate a repair-to-perform model for an additional asset based on at least one of a collection of data (e.g., portion of historic data, portion of sensor data, among others) for a first asset. The repair-to-perform model can be generated from a first asset and used for an additional asset based on a relationship (discussed below). For instance, the repair evaluation component can indicate a repair to perform on a first asset based on collected information associated with the first asset. The model component can create a repair-to-perform model for an additional asset based on the indicated repair(s) for the first asset. Thus, the indicated repair(s) for each asset can be leveraged to be used for additional assets based on various factors, conditions, or definitions. This relationship between an asset (e.g., the first asset) and an additional asset can extend the use and predictability for identifying repairs for assets.

In an embodiment, a repair can be indicated for an additional asset based on a relationship with an asset, wherein the repair evaluation component has indicated a repair to perform on the asset and the relationship between the additional asset and the asset is to have a substantially similar condition of use. By way of example and not limitation, the condition of use can be associated with a location of the asset, a weather condition for a location of the asset, a cargo load related to the asset, a duration of time the asset is used, among others. In an embodiment, the relationship can be a substantially similar asset type between the additional asset and the asset (e.g., type, model, make, brand, year, function, among others). For instance, a generic asset and a name brand asset can be utilized as relationship in which one is used to model the other and repair(s) are indicated for both the generic asset and the name bran asset (or a combination thereof).

In an embodiment, the additional asset can be comparable or substantially similar to the first asset (e.g., first vehicle of brand A and model B and a second vehicle of brand A and model B, first vehicle of brand A and model B and a first vehicle of brand A and model C, among others). In another embodiment, the additional asset can be used in a similar or comparable environment of the first asset (e.g., first asset used in location A and additional asset used in location A, first asset used in location A and additional asset used in location B, where A and B are similar or comparable, and the like). In an embodiment, the additional asset can include a similar condition of use with the first asset.

In an embodiment, the evaluate component, the model component, and/or the repair evaluation component or other discussed components or elements (e.g., CRB database, MMS database, cost component, among others) stores information related to the systems 100, 200, 300, and/or 400 with a data store 320. The data store can include information such as, but not limited to, asset information, repair information, sensor data, detector information, repair information, conditions of use for assets, repair history data, among others, and/or a suitable combination thereof.

It is to be appreciated that the data store can be, for example, either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The data store of the subject systems and methods is intended to comprise, without being limited to, these and other suitable types of memory. In addition, it is to be appreciated that the data store can be a server, a database, a hard drive, a flash drive, an external hard drive, a portable hard drive, a cloud-based storage, and the like.

FIG. 4 is an illustration of a system 400 for ascertaining a cost associated with a repair to perform on an asset. The system can include a cost component 410 that can be configured to evaluate a cost of a repair indicated by the repair evaluation component. The cost component can provide real time estimates for pricing of parts and/or repair(s) for a vehicle. For instance, upon indication of a repair to perform, the cost component can retrieve pricing information based on, but not limited to, historic data related to the repair performed in the past, pricing information from a repair facility, contract billing information between a repair and a repair facility, among others. In an embodiment, the cost component can evaluate historic pricing information for at least one of a part, a repair, a repair facility, a type of repair at a repair facility, among others. Although depicted as a stand-alone component, the cost component can be incorporated into the evaluate component, incorporated into the repair evaluation component, or a combination thereof.

In an embodiment, a system is provided that includes at least the following: means for evaluating a portion of sensor data related to an asset (e.g., system 100, component, controller, evaluate component, among others); means for evaluating a portion of historic data associated with a repair to the asset (e.g., system 100, component, controller, evaluate component, among others); and means for indicating a repair to perform on the asset based on at least one of the portion of sensor data or the portion of historic data (e.g., system 100, component, controller, repair evaluation component, among others).

The aforementioned systems, components, (e.g., evaluate component, repair evaluation component, among others), and the like have been described with respect to interaction between several components and/or elements. It should be appreciated that such devices and elements can include those elements or sub-elements specified therein, some of the specified elements or sub-elements, and/or additional elements. Further yet, one or more elements and/or sub-elements may be combined into a single component to provide aggregate functionality. The elements may also interact with one or more other elements not specifically described herein.

In view of the exemplary devices and elements described supra, methodologies that may be implemented in accordance with the disclosed subject matter will be better appreciated with reference to the flow chart of FIG. 5. The methodologies are shown and described as a series of blocks, the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the methods described hereinafter. The methodologies can be implemented by a component or a portion of a component that includes at least a processor, a memory, and an instruction stored on the memory for the processor to execute.

FIG. 5 illustrates a flow chart of a method 500 for identifying a repair to perform on an asset. At reference numeral 510, a portion of sensor data related to an asset can be evaluated. At reference numeral 520, a portion of historic data associated with a repair to the asset can be evaluated. At reference numeral 530, a repair to perform on the asset can be indicated based on at least one of the portion of sensor data or the portion of historic data.

The method can further include identifying at least one of a date or a time to perform the repair on the asset. The method can further include generating an estimated cost for the indicated repair based on at least one of the portion of sensor data or the portion of historic data. The method can further include receiving the portion of historic data from a Maintenance Management System (MMS) database. The method can further include receiving the portion of historic data from a Car Repair Billing (CRB) database. The method can further include collecting the portion of sensor data for the asset from at least one of a wheel input, a load detector, a hot bearing detector, a dragging equipment, a real time sensor, a wheel degrade sensor, a flat spot detector, or an equipment health data sensor. The method can further include collecting conditions of use data related to the asset. The method can further include the conditions of use data are associated with a location of the asset, a weather condition for a location of the asset, a cargo load related to the asset, or a duration of time the asset is used.

The method can further include modeling a schedule for a repair for an additional asset based on at least one of the portion of the sensor data or the portion of historic data. The method can further include the additional asset to include a substantially similar condition of use data of the asset. The method can further include communicating information including at least one of an asset identification, the indicated repair, an estimated time of the repair, a part associated with the repair, and a cost of the repair. The method can further include adjusting a manufacturer suggested indicator to perform a repair based on at least one of the portion of sensor data or the portion of historic data. The method can further include generating an indicator to perform the indicated repair on the asset, the indicator relates to at least one of the asset or a part associated with the indicated repair. The method can further include the indicator being at least one of a duration of use, a duration of time, a measurement of distance traveled for the asset, or a failure rate. The method can further include utilizing the indicator to perform a repair on two or more assets.

In embodiments, one or more of the methods set forth herein are carried out (at least partially automatically) with one or more components, that is, by hardware, software, or a combination thereof configured for execution of the method. For example, in one embodiment, a method comprises evaluating, with at least one component, a portion of sensor data related to an asset. The method further comprises evaluating, with the at least one component, a portion of historic data associated with at least one historic repair to the asset. The method further comprises indicating, with the at least one component, a future repair to perform on the asset based on at least one of the portion of sensor data or the portion of historic data. (“With at least one component” means all the steps may be carried out by one component, that each step may be carried out by a different component, or that some steps are carried out by one component and other steps are carried out by one or more other, different components.)

In the specification and claims, reference will be made to a number of terms that have the following meanings. The singular forms “a”, “an” and “the” include plural referents unless the context clearly dictates otherwise. Approximating language, as used herein throughout the specification and claims, may be applied to modify a quantitative representation that could permissibly vary without resulting in a change in the basic function to which it is related. Accordingly, a value modified by a term such as “about” is not to be limited to the precise value specified. In some instances, the approximating language may correspond to the precision of an instrument for measuring the value. Moreover, unless specifically stated otherwise, a use of the terms “first,” “second,” etc., do not denote an order or importance, but rather the terms “first,” “second,” etc., are used to distinguish one element from another.

As used herein, the terms “may” and “may be” indicate a possibility of an occurrence within a set of circumstances; a possession of a specified property, characteristic or function; and/or qualify another verb by expressing one or more of an ability, capability, or possibility associated with the qualified verb. Accordingly, usage of “may” and “may be” indicates that a modified term is apparently appropriate, capable, or suitable for an indicated capacity, function, or usage, while taking into account that in some circumstances the modified term may sometimes not be appropriate, capable, or suitable. For example, in some circumstances an event or capacity can be expected, while in other circumstances the event or capacity cannot occur—this distinction is captured by the terms “may” and “may be.”

This written description uses examples to disclose the invention, including the best mode, and also to enable one of ordinary skill in the art to practice the invention, including making and using a devices or systems and performing incorporated methods. The patentable scope of the invention is defined by the claims, and may include other examples that occur to one of ordinary skill in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differentiate from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal language of the claims.

Claims

1. A method, comprising:

evaluating, with at least one component, a portion of sensor data related to an asset;

evaluating, with the at least one component, a portion of historic data associated with at least one historic repair to the asset; and

indicating, with the at least one component, a future repair to perform on the asset based on at least one of the portion of sensor data or the portion of historic data.

2. The method of claim 1, further comprising identifying at least one of a date or a time to perform the future repair on the asset in order to mitigate damage of the asset.

3. The method of claim 1, further comprising generating an estimated cost for the future repair based on at least one of the portion of sensor data or the portion of historic data.

4. The method of claim 3, further comprising receiving the portion of historic data from at least one of a Maintenance Management System database or a Car Repair Billing (CRB) database.

5. The method of claim 1, further comprising collecting conditions of use data related to the asset, wherein the conditions of use data is associated with at least one of a location of the asset, a weather condition for a location of the asset, a cargo load related to the asset, or a duration of time the asset is used;

wherein the future repair is indicated based on the portion of sensor data, the portion of historic data, and the conditions of use data; and

wherein the portion of sensor data is from at least one of a wheel input, a load detector, a hot bearing detector, a dragging equipment, a real time sensor, a wheel degrade sensor, a flat spot detector, or an equipment health data sensor associated with the asset.

6. The method of claim 1, further comprising receiving the portion of sensor data for the asset from at least one of a wheel input, a load detector, a hot bearing detector, a dragging equipment, a real time sensor, a wheel degrade sensor, a flat spot detector, or an equipment health data sensor.

7. The method of claim 1, further comprising collecting first conditions of use data related to the asset, wherein first conditions of use data is utilized to facilitate indicating the future repair.

8. The method of claim 7, wherein the first conditions of use data is associated with at least one of a location of the asset, a weather condition for a location of the asset, a cargo load related to the asset, or a duration of time the asset is used.

9. The method of claim 8, further comprising:

scheduling an additional repair for an additional asset based on at least one of the portion of sensor data or the portion of historic data; and

scheduling the additional repair a second conditions of use data.

10. The method of claim 9, wherein second conditions of use data related to the additional asset is substantially similar to the first conditions of use data of the asset.

11. The method of claim 1, further comprising communicating information including at least one of an asset identification, the future repair, an estimated time of the future repair, a part associated with the future repair, or a cost of the future repair.

12. The method of claim 1, further comprising adjusting a manufacturer suggested indicator to perform the future repair based on at least one of the portion of sensor data or the portion of historic data.

13. The method of claim 1, further comprising generating an indicator to perform the future repair on the asset, wherein the indicator relates to at least one of the asset or a part associated with the future repair.

14. The method of claim 13, wherein the indicator is at least one of a duration of use, a duration of time, a measurement of distance traveled for the asset, or a failure rate.

15. The method of claim 14, further comprising utilizing the indicator to perform the future repair on two or more assets.

16. A system comprising:

a first component configured to collect at least one of a portion of sensor data related to an asset or a portion of historic data related to a historic repair performed on the asset; and

a second component configured to identify an indicator to perform a future repair on two or more assets based on at least one of the portion of sensor data collected by the first component or the portion of historic data collected by the first component.

17. The system of claim 16, further comprising a third component configured to schedule the future repair for one of the two or more assets.

18. The system of claim 16, wherein the indicator relates to the one of the two or more assets or a part used for the future repair and the indicator is at least one of a duration of use, a duration of time, a measurement of distance traveled for one of the two or more assets, or a failure rate.

19. The system of claim 16, wherein the second component is configured to dynamically adjust a manufacturer suggested indicator to perform the future repair based on at least one of the portion of sensor data or the portion of the historic data, wherein the manufacturer suggested indicator is defined by a manufacturer of one of the two or more assets.

20. A system, comprising:

means for evaluating a portion of sensor data related to an asset;

means for evaluating a portion of historic data associated with a repair to the asset; and

means for indicating a repair to perform on the asset based on at least one of the portion of sensor data or the portion of historic data.