CN103177328A - Remote telematic microfluidic analysis using handheld device - Google Patents

Abstract

A fluid analysis system includes a handheld device and a management system. The handheld device includes a fluid analysis control module and a remote information device. The fluid analysis control module is configured to initiate sampling of fluid and provide the sample to a microfluidic analyzer for microfluidic analysis. The telematics device is coupled to the fluid analysis control module and constructed with a wireless transceiver. The management system is located remotely from the telematics device and is configured to wirelessly receive the results of the microfluidic analysis transmitted from the telematics device.

Description

Telematics Microfluidic Analysis Using a Handheld Device

Cross-references to related applications (continuation-in-part)

This application claims a filing date of May 16, 2011, entitled "TELEMATIC ASSET MICROFLUIDIC ANALYSIS," by David Poling et al., Attorney Docket No. TRMB-2888, Serial No. 13/108,983, assigned to the assignee of this application priority to and continuation-in-part of a co-pending patent application, the disclosure of which is incorporated herein by reference.

Cross References to Related Applications

This application is related to U.S. Patent Application filed ( ), Attorney Docket No. TRMB-2888.CIP2 of Jeff Hamilton, serial number ( ), entitled "Telematic Locomotive Microfluidic Analysis," and assigned to the assignee of the present application.

This application and Attorney Docket No. TRMB-1925 of Daniel Wallace, filed May 7, 2007, entitled "System and Method of Management," Serial No. 11/801,093 assigned to the assignee of this application U.S. patent application related.

This application and the filing date is May 7, 2007, the attorney file number is TRMB1903, the title is "System and Method for Providing Asset Management Information to a Customer", the serial number is 11/801,060 and it is assigned to the assignee of this application U.S. patent application related.

This application and U.S. Patent No. 11/801,041, filed May 7, 2007, Attorney Docket No. TRMB1900, entitled "Method for Providing Status Information Pertaining to an Asset" and assigned to the assignee of this application Application related.

This application is related to U.S. Patent Application Serial No. 11/801,061, filed May 7, 2007, Attorney Docket No. TRMB1897, entitled "Enabling Notifications Pertaining to an Asset," assigned to the assignee of this application .

This application is related to U.S. Patent Application Serial No. 11/801,091, Attorney Docket No. TRMB1920, entitled "Receiving Information Pertaining to a Construction Project," filed May 7, 2007, and assigned to the assignee of this application relevant.

This application is related to U.S. Patent Application Serial No. 11/801,101, filed May 7, 2007, Attorney Docket No. TRMB1902, entitled "Limiting Access to Asset Management Information," assigned to the assignee of the present application .

This application is related to U.S. Patent Application No. TRMB 1927, filed May 7, 2007, entitled "Externally Augmented Asset Management," Serial No. 11/801,014, assigned to the assignee of the present application.

This application is related to U.S. Patent Application Serial No. 11/801,090, filed May 7, 2007, Attorney Docket No. TRMB 1894, entitled "Impromptu Asset Tracking," and assigned to the assignee of the present application.

This application is related to U.S. Patent Application No. TRMB 1896, filed May 7, 2007, entitled "Integrated Asset Management," Serial No. 11/801,017, assigned to the assignee of the present application.

This application is related to U.S. Patent Application Serial No. 11/801,019, filed May 7, 2007, Attorney Docket No. TRMB1901, entitled "Utilizing Historical Data in an Asset Management Environment," and assigned to the assignee of the present application relevant.

This application is related to U.S. Patent Application Serial No. 11/801,077, filed May 7, 2007, Attorney Docket No. TRMB1898, entitled "Method for Automatic Asset Classification," and assigned to the assignee of the present application.

This application and U.S. Patent No. 11/801,089, filed May 7, 2007, Attorney Docket No. TRMB1899, entitled "Method for Controlling Power Usage of a Reporting Device" and assigned to the assignee of this application Application related.

This application and U.S. Patent No. 11/801,116, filed May 7, 2007, Attorney Docket No. TRMB1819, entitled "Method for Delivering Tailored Asset Information to a Device" and assigned to the assignee of this application Application related.

This application and U.S. Patent No. 11/801,092, filed May 7, 2007, Attorney Docket No. TRMB1928, entitled "Method for Enhancing Revenue Generation for a Manufactured Asset" and assigned to the assignee of this application Application related.

This application is related to U.S. Patent Application Serial No. 11/901,088, filed May 7, 2007, Attorney Docket No. TRMB1926, entitled "Detecting Construction Equipment Process Failure," and assigned to the assignee of this application, And this application was granted US Patent 7,898,403 on March 1, 2011.

This application is related to U.S. Patent Application Serial No. 11/901,554, filed September 17, 2007, Attorney Docket No. TRMB2220, entitled "Unreported Event Status Change Determination and Alerting," assigned to the assignee of this application .

Background technique

Currently, cutting-edge operating venues do not always track advances in technology across domains. For example, shops that rent or sell the latest gadgets to manage their business using methods such as pen and paper or computing systems that are three to five generations behind current computing technology are still common. One of the main tenets of relying on antiquated management systems is "if it ain't broke, don't fix it".

However, with the advancement of modern technology, many enterprises are realizing the advantages of some products and dividing them into legacy systems. For example, a leasing company may lease an asset with an initial lease contract printed out on an early personal computer running a DOS program. Also, when the leased item is returned, the same leasing company can use the paper-and-pencil method to accept the vehicle and place it back in the system. That is, there will be batches of walkers walking around the returned asset and visually inspecting the asset for maintenance issues, any damage, engine hours, total mileage, etc.

Each of these metrics can be used by batch walkers to determine whether an asset needs any repairs or other aspects that require attention before being returned to the rental fleet. The response is then written on a piece of paper and attached to the returned asset. In some cases, an asset may require more than one type of aspect of attention, making inherently multiple sheets of paper attached to the asset. The asset is then reallocated accordingly and may be returned to the lease lot at a later date. Also, because assets are acquired through different return-lease status processes, paper may need to be updated, augmented, or otherwise manipulated.

Also, leased assets can have built-in Global Navigation Satellite System (GNSS) receivers attached. For example, the rental company may have attached GNSS, or the asset may have arrived with attached GNSS, in order to reduce the cost of insurance, aid in stolen property recovery, etc. In some cases, a user operating an asset may use GNSS to find directions from one location to another, or GNSS may be used to find the location of an asset. For example, law enforcers may use GNSS to recover stolen assets; emergency personnel may use GNSS to locate assets to provide assistance or assistance; and so on.

Although the management method described herein uses a leasing company as an example, issues related to asset management are not limited to leasing companies. Operating companies may have the same asset management agreements and issues. For example, a company may have assets that are verified and sent to the site by an operator grabbing the asset and walking it. In the same way, assets can be returned to the lot and the operator returns only the key to the storage location. So after the asset is gone, the only way to know what the asset did during the day, whether the asset was in the right place, or even if it was used for the right job involves contacting the operator during the workday, or asking at the end of the day operator.

With lower margins in asset handling industries such as construction, properly managing assets has become even more important. For this reason, most asset handling industries require their employees to carry their phones with them. In this way, when the asset is on site, the operator can be contacted and advised where to operate the asset and what work should be performed.

However, this method of command and control is disadvantageous and unreliable. For example, the operator may not know where the asset is, or may have been told the wrong location of the asset. Additionally, operators may misrepresent jobs that are being performed, or spend more time on outages than actually operating the asset. Each of these errors and omissions will further impact the already razor-thin margins faced by the asset handling industry.

Furthermore, many assets (including, for example, vehicles and other construction equipment machines as described herein) have fluids that are critical to their continued and proper operation. These fluids are often analyzed to determine, based on the chemical/metallurgical content of the analyzed fluid, whether the fluid in question maintains the properties required for proper operation of the asset and to determine the wear characteristics of the asset. For example, fluid analysis is often performed during routine preventive maintenance to provide information related to lubricant and machine condition. By tracking the analysis results over the life of the machine, trends can be established and/or monitored in a manner that helps eliminate or predict the need for maintenance.

Typically, after obtaining a fluid sample from an asset, a technician needs to mail or otherwise physically transmit the fluid sample to a remote laboratory. Laboratory-on-a-chip ("LOC") devices do exist that can facilitate this process by integrating one or more of a variety of experimental functions on a single chip. A microfluidic analyzer can be an example of a LOC. Microfluidic analyzers are commonly found in the biotechnology domain because they enable technicians to analyze fluids in person without sending the results to remote laboratories. Trained field technicians are also able to use the LOC device and microfluidic analysis techniques to analyze samples of asset fluids located in situ without sending asset fluid samples to remote laboratories for analysis.

Often, end users of assets are not skilled in fluid analysis or even in fluid sampling protocols. In numerous other programs, there may be problems in the absence of any personnel trained, capable, or even known to perform analysis and/or fluid sampling, for example, if the asset is being used at a remote location, where access to the job site is difficult, and/or when the asset is leased out or used on a long-term basis.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this application, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention. Unless indicated, the drawings referred to in this specification should be understood as not drawn to scale.

Figure 1 is a block diagram of an exemplary computer system used in accordance with one embodiment of the present invention.

Figure 2A is a network diagram of an exemplary asset management method according to one embodiment of the present invention.

Figure 2B is a network diagram of an exemplary asset management method including an asset information report generator and its modules according to one embodiment of the present invention.

Figure 3 is a block diagram of an exemplary asset management system in accordance with one embodiment of the present invention.

Figure 4 is a flowchart of an exemplary asset management method according to one embodiment of the present invention.

5 is a block diagram of an exemplary GUI display of an asset information report generated by an asset management system in accordance with one embodiment of the present invention.

6 is a block diagram of an exemplary printable format of an asset information report generated by an asset management system in accordance with one embodiment of the present invention.

Figure 7 is a block diagram of an exemplary asset management system communicatively coupled with a customer application in accordance with one embodiment of the present invention.

Figure 8 is a flowchart of an exemplary method for providing asset management information to customer applications in accordance with one embodiment of the present invention.

Figure 9 is an expanded block diagram of an asset information report generator for use with an exemplary asset management system in accordance with one embodiment of the present invention.

Figure 10 is a flowchart of an exemplary method for providing customized asset management in accordance with one embodiment of the present invention.

11 is a block diagram of an exemplary printable format of a custom asset information report generated by an asset management system in accordance with one embodiment of the present invention.

Figure 12 depicts an asset management system in communication with customers according to one embodiment of the present invention.

Figure 13 is a flowchart of a method for restricting access to asset management information, according to one embodiment.

Figure 14 depicts an asset management system for enabling asset-related notifications, according to one embodiment.

Figure 15 is a diagram of an example of an asset-related state machine, according to one embodiment.

Figure 16 is a flowchart of a method for enabling asset-related notifications, according to one embodiment.

17 depicts a block diagram of associating different types of reporting sources with different assets based on asset characteristics and objectives of a construction project, according to one embodiment.

Figure 18 depicts a block diagram of an installable reporting source, according to one embodiment.

Figure 19 depicts an asset management system for receiving information related to a construction project, according to one embodiment.

20 is a flowchart of a method for receiving information related to a construction project, according to one embodiment.

21 is a block diagram depicting the relationship between a manufacturer of a construction asset, a leasing company that leases the construction asset, and a construction company, according to one embodiment.

Figure 22 depicts various assets that two construction companies have leased from a vendor and a service truck owned by the vendor, according to one embodiment.

Figure 23 depicts a block diagram of an asset management system according to one embodiment.

Figure 24 is a diagram illustrating the use of rights to limit access to asset management information, according to one embodiment.

Figure 25 is a flowchart of a method for restricting access to asset management information, according to one embodiment.

Figure 26 is a network diagram of an exemplary method for externally extending asset management in accordance with one embodiment of the present invention.

Figure 27 is a block diagram of an exemplary externally-extended asset management system communicatively coupled with an optional customer application in accordance with one embodiment of the present invention.

Figure 28 is a flowchart of an exemplary method for providing externally scaled asset management in accordance with one embodiment of the present invention.

Figure 29 is a block diagram of an exemplary asset management system used as a temporary asset tracking system in accordance with one embodiment of the present invention.

Figure 30 is a flowchart of an exemplary method for temporarily tracking the location of an asset in accordance with one embodiment of the present invention.

Figure 31 is a diagram of an exemplary implementation for temporarily tracking asset location in accordance with one embodiment of the present invention.

Figure 32 is a block diagram of an exemplary printable format of an asset information report generated by an asset management system in accordance with one embodiment of the present invention.

33 is a block diagram of an exemplary GUI display of an asset information report generated by an asset management system in accordance with one embodiment of the present invention.

Figure 34 is a block diagram of an exemplary asset management system according to one embodiment of the present invention.

Figure 35 is a flowchart of an exemplary method for integrating asset management information according to one embodiment of the present invention.

Figure 36 is a block diagram of an exemplary asset returned to an asset leasing company in accordance with one embodiment of the present invention.

Figure 37 is a flowchart of an exemplary method for providing integrated asset management information in accordance with one embodiment of the present invention.

Figure 38 is a block diagram of an exemplary asset management system configured with an optional processing error detector in accordance with one embodiment of the present invention.

39 is a flowchart of an exemplary method for detecting construction equipment processing errors in accordance with one embodiment of the present invention.

FIG. 40 illustrates an exemplary construction equipment asset in conjunction with a front view of a pile of materials at a construction site.

Figure 41 illustrates an exemplary processing error report displayed on an exemplary receiving device in accordance with one embodiment of the present invention.

Figure 42 is a block diagram of an exemplary asset information report generator in accordance with one embodiment of the present invention.

Figure 43 is a block diagram of an exemplary printable format of a custom asset information report generated by an asset management system in accordance with one embodiment of the present invention.

Figure 44 is a flowchart of an exemplary method of using historical data in an asset management environment according to one embodiment of the invention.

Figure 45A is a block diagram of an exemplary reporting source coupled to an asset, according to one embodiment of the invention.

Figure 45B is a diagram of an exemplary reporting device according to one embodiment of the present invention.

Figure 46 is a block diagram of an exemplary system for automatically classifying assets according to one embodiment of the present invention.

Figure 47 is a flowchart of an exemplary method for automatically associating assets with graphical representations in accordance with one embodiment of the invention.

Figure 48 is a flowchart of an exemplary method for automatically categorizing assets in accordance with one embodiment of the present invention.

49A is an illustration of an exemplary system for controlling power usage of a stationary reporting device, according to one embodiment of the invention.

49B is an illustration of an exemplary system for controlling power usage of a mobile reporting device, according to one embodiment of the invention.

Figure 50 is a flowchart of an exemplary method for managing power and reporting status changes of reporting devices in accordance with one embodiment of the present invention.

51 is a flowchart of an exemplary method for managing power to a reporting device in response to detecting movement of an asset in accordance with an embodiment of the invention.

52 is a block diagram of an exemplary system for controlling power usage of a reporting device in accordance with an embodiment of the present invention.

Figure 53A is a block diagram of an exemplary handheld computing device according to one embodiment of the present invention.

Figure 53B is a block diagram of an exemplary computer system according to one embodiment of the present invention.

Figure 54A is a block diagram of an exemplary list of top-level user-selectable options for defining a GUI dashboard, according to one embodiment of the present invention.

Figure 54B is a block diagram of an exemplary list of secondary user selectable options for defining a GUI dashboard, according to one embodiment of the present invention.

Figure 55A is a block diagram of an exemplary top-level user-defined GUI dashboard in accordance with one embodiment of the present invention.

Figure 55B is a block diagram of an exemplary second-level user-defined GUI dashboard in accordance with one embodiment of the present invention.

Figure 56 is a flowchart of an exemplary method for communicating adjusted asset information to a device in accordance with one embodiment of the invention.

57 is a diagram of an example of assets coupled with an electronic control module, a fluid analysis control module, and a telematics device, according to various embodiments.

58 is a block diagram of an example of a telematics asset microfluidic analysis system in accordance with various embodiments.

Figure 59 illustrates an example of a system providing fluid analysis results, according to an embodiment.

60A-60D illustrate a flowchart of an exemplary method of analyzing a fluid, according to various embodiments.

61 is a block diagram of an example of a handheld telematics microfluidic analysis system, according to various embodiments.

Figure 62 illustrates an example of a handheld telematics microfluidic analysis system comprising a single microfluidic analyzer, according to an embodiment.

Figure 63 illustrates an example of a handheld telematics microfluidic analysis system comprising multiple microfluidic analyzers, according to an embodiment.

64A-64D illustrate a flowchart of an example method of analyzing a fluid, according to various embodiments.

Detailed ways

Reference will now be made in detail to various embodiments of the invention, examples of which are illustrated in the accompanying drawings. While the invention will be described in conjunction with these embodiments, it will be understood that they are not intended to limit the invention to these embodiments. On the contrary, the invention is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the invention as defined by the appended claims. Furthermore, in the following description of the invention, numerous specific details are set forth in order to provide a thorough understanding of the invention. In other instances, well-known methods, procedures, objects and circuits have not been described in detail so as not to unnecessarily obscure aspects of the present invention.

example computer system

Referring now to FIG. 1, a block diagram of an embodiment of an exemplary computer system 100 for use in accordance with the present invention. It should be understood that computing system 100 is not strictly limited to a computer system. Thus, the computing system 100 of the present embodiment may be adapted for any type of computing device (eg, server computer, portable computing device, desktop computer, mobile telephone, radio pager, personal digital assistant, etc.). In this discussion of the present disclosure, processes and steps are discussed which, in one embodiment, are implemented as a series of instructions residing in computer readable memory and executed by a processor of computing system 100 (e.g., software program). When executed, the instructions cause the computer system 100 to perform specific actions and exhibit specific behaviors, as will be described in detail herein.

Computer system 100 of FIG. 1 includes an address/data bus 110 for communicating information, and one or more central processing units 102 coupled with bus 110 for processing information and instructions. Central processing unit 102 may be a microprocessor or any other type of processor. Computer system 100 also includes data storage features, such as: computer usable volatile memory unit 104 (e.g., random access memory, static RAM, dynamic RAM, etc.), which is coupled to bus 110 for storing 102 information and instructions; computer usable non-volatile memory unit 106 (e.g., read-only memory, programmable ROM, flash memory, EPROM, EEPROM, etc.), which is coupled to bus 110 for storing 102 static information and instructions. The computer system 100 also includes one or more signal generating and receiving devices 108 coupled to the bus 110 to enable the computer system 100 to interface with other electronic devices and computer systems. The communication interface 108 of this embodiment may include wired and/or wireless communication technologies.

Optionally, computer system 100 may include an alphanumeric input device 114 including alphanumeric keys and function keys, coupled to bus 110 for communicating information and command selections to the central processing unit 102. Computer system 100 may include an optional cursor control or cursor guide 116 coupled to bus 110 for communicating user input information and command selections to central processing unit 102 . Cursor directing device 116 may be implemented using a variety of well-known devices such as a mouse, trackball, track pad, optional tracking device, and touch screen, among many other devices. Alternatively, it will be appreciated that a cursor may be directed and/or activated via input from the alphanumeric input device 114 using dedicated keys and key sequence commands. This embodiment is also suitable for directing the cursor by other means such as for example voice commands.

Computing system 100 of FIG. 1 may also include one or more optional computer-usable data storage devices 118, such as magnetic or optical disks and disk drives (e.g., hard drives or floppy disks), coupled to bus 110 for storing information and instruction. An optional display device 112 may be coupled to bus 110 of computing system 100 for displaying video and/or graphics. It should be appreciated that the optional display device 112 may be a cathode ray tube (CRT), flat panel liquid crystal display (LCD), field emission display (FED), plasma display, or any other suitable for displaying user-recognizable video and/or or a display device for graphic images and alphanumeric characters.

Construction Services Industry

The construction services industry is an industry comprised of both horizontal and vertical players. Usually, horizontal actors are those who engage in some kind of practical activity on the construction site, while vertical actors usually play the role of direct enablers of horizontal actors. In some cases, a single person or entity may be considered a horizontal participant, a vertical participant, or both, depending on the nature of the activities being undertaken. Various embodiments of the invention described below relate to participants in the construction services industry.

销售商、John Deere销售商等)、建筑承包方(既含总承包方，又含分承包方)、建筑材料供应商(例如，诸如砾石、钢、混凝土、木材、干墙、沥青等的供应商)、建筑设备租赁公司、建筑设备维护公司、勘测公司(在施工现场作业时)、地质学者(在施工现场作业时)、市政工程公司、建筑项目管理公司，等等。Examples of horizontal actors include, but are not limited to: machine suppliers (eg,

Vendors, John Deere Vendors, etc.), Construction Contractors (both general contractors and subcontractors), construction material suppliers (for example, suppliers of materials such as gravel, steel, concrete, lumber, drywall, asphalt, etc.) business), construction equipment rental companies, construction equipment maintenance companies, survey companies (when working on construction sites), geologists (when working on construction sites), municipal engineering companies, construction project management companies, etc.

Examples of vertical players include, but are not limited to: construction insurance companies (e.g., companies that insure construction equipment, job completion, accidents, etc.), safety supervision companies, construction project management software vendors, fuel suppliers, construction material suppliers , machine suppliers, geologists, surveyors, municipal engineering companies, construction project management companies, construction equipment rental companies, construction equipment maintenance companies, contractors, etc.

Part I: Asset Management

overview

Embodiments described herein provide methods and systems for asset management. In general, the embodiments described herein use multiple disparate sources for monitoring assets. Each disparate source provides an asset report, which is aggregated in the database. Organize the database to combine multiple asset reports for an organized single source of asset information. The resulting database will provide ample asset management data with a depth significantly greater than a single source of information can provide.

Furthermore, by utilizing multiple disparate sources to provide information, asset managers' visibility into assets is significantly increased, while the likelihood of asset loss due to asset source reporter failures is significantly reduced. In other words, failure of a single asset source reporter will not result in a complete loss of the asset manager's asset management capabilities.

Furthermore, due to the asset management capabilities described herein, important business management tools are implemented. That is, because asset management systems can be used for all levels of asset management, asset management systems provide significant value-added features at the manufacturing level, lease/lease level, and owner level. Also, the value-added features are likely to be "self-selling" features.

For example, this example will focus on an exemplary supermarket building. Although the following examples are provided in the context of the construction domain, the asset management system described herein is applicable to assets other than buildings. The use of building assets provides a multifaceted example and is used herein for the purposes of brevity and clarity only.

In a construction business, there are various assets required to complete a project such as building a supermarket. First, the site must be surveyed and marked; this requires survey equipment. Next, the site must be cleared and leveled; this requires grinders, levelers, bulldozers, saws, chip trucks, and more. After the site is cleared and leveled, construction can begin; this requires excavators, pavers, concrete mix trucks, feeder trucks, cranes, tools, and more. Even for this exemplary construction site, the quantity and cost of all the assets required are significant.

Due to the high cost and specialization of much of the construction equipment used on supermarket construction sites, construction companies may own some assets, lease some assets, and lease some assets out, depending on the company and the cost/availability of the asset in question. For example, it may be cheaper to lease or rent out an asset that is rarely used than to buy it, and it may be cheaper to buy a frequently used asset than to lease or rent it out.

This asset management system is beneficial in all aspects of owning, renting out, leasing and manufacturing. For example, as detailed herein, asset management systems enable users to track assets, including their location and operation. In this way, maintenance schedules can be provided by the asset management system. Additionally, excessive wear and tear or unplanned maintenance needs will also be identified by the asset management system.

Thus, because asset location is also tracked by the asset management system, when maintenance is or will be required, maintenance requirements will be known and the location of the asset will also be known. Therefore, maintenance on the machine can be performed on site. This results in significant reductions in asset downtime, parts order delays, overworked machines, and more.

For example, if a bulldozer is operating at peak operation for an extended period of time (such as disaster relief), the asset management system will be aware of planned maintenance requirements and update its future maintenance forecast based on the increase in current operating hours. As a result, when scheduled maintenance is due, the dozer can be serviced as needed in the field without intentional or deliberate skipping of scheduled maintenance intervals as is currently done.

Also, because of the maintenance and other information tracked by the asset management system described herein, manufacturers can begin offering planned/unplanned maintenance programs along with their sales or leases. For example, a manufacturer may sell bulldozers to a construction equipment company. Manufacturers will then use an asset management system to track assets. When scheduled maintenance is due, the manufacturer can call the buyer to plan the maintenance or can go on site to visit the asset and do the scheduled maintenance during the bulldozer downtime.

For example, an asset management system might notice that a bulldozer is scheduled to operate from 6 a.m. to 8 p.m. seven days a week. This allows the manufacturer to visit the dozer on site during the hours of 9:00 p.m. to 5:00 a.m. for planned maintenance without hindering the operation of the dozer. When doing so, the manufacturer will realize the additional revenue of maintenance contracts, and the purchaser will realize the additional benefit of reduced asset downtime.

However, service contracts are not limited to manufacturers. Rental companies can use the same methods described above to provide the same services to renters. In addition, the leasing company can track the operation and location of the asset to ensure that lease contract rules are not violated and the asset is not being operated in a harmful manner. For example, the leasing company can track any stress placed on the asset, the speed at which the asset is being operated, any unplanned maintenance issues with the asset that the lessor may have overlooked or not been aware of, and more. In this way, the asset management system provides the leasing company with asset security and potentially reduced emergency repairs, in addition to the added benefit of providing service contract containment while the lessee realizes reduced operational downtime for the leased asset.

In a similar manner, the owner of an asset can also take advantage of the advantages stated above to ensure proper equipment handling, monitor operators using the equipment, manage planned/unplanned maintenance of the asset, and the like.

Furthermore, the manufacturer/rental agency/owner can also use the asset management system to track the location of assets to eliminate the possibility of misuse and to expedite the recovery of stolen or lost items. For example, areas such as ground fences detailed herein may establish where assets should be located. When an asset leaves an established area, the asset management system can provide an alert related to the event. The user will then be able to view the location of the asset and notify the correct party of the incident. For example, in the case of theft, the police can be contacted, while in the event the operator leaves the scene unintentionally, the operator can be contacted to quickly resolve the problem and reduce any collateral damage that may occur.

Due to significant advantages such as cost savings, less downtime of assets, asset management systems have the potential to popularize their own distribution. For example, initially a manufacturer may use an asset management system. In this way, buyers will quickly realize that planned maintenance is taking place during regular asset downtime and that unscheduled maintenance is happening before the asset is completely damaged or the problem becomes exacerbated. Specifically, buyers will be concerned with how the manufacturer will know when planned maintenance is due or problems are occurring. Once buyers realize the increase in operating time, the reduction in missed maintenance costs, etc., buyers will want to have the same insight for their own assets.

This same business approach applies to lessor models where lessors focus on the capabilities of the leasing agency. The approach can even be extended to this peer-to-peer model: one asset maker/lessor/owner notices that another asset maker/lessor/owner has generated new maintenance revenue, reduced asset downtime, due to Regular maintenance increases the useful life of assets, etc.

Asset Management Network

Referring now to FIG. 2A, a network diagram of an exemplary asset management method in accordance with one embodiment of the present invention is shown. Asset management network 200 includes database 205 and number of reporting sources 208 .

Database 205 receives information from at least two reporting sources 208 and organizes data within database 205 to enable determination of asset-related information. For example, data within database 205 may be organized to enable determination or access of information related to a particular asset or assets.

In one embodiment, database 205 is a single database located on a single computing system, such as computing system 100 . In another embodiment, database 205 may actually consist of multiple databases on a single computing system or multiple computing systems. Also, multiple databases may be co-located or spread across multiple locations. In addition, multiple databases can be coupled together by wire or wireless to form a database network, and asset information can be stored on the database network. In one embodiment, an asset may be a mechanical device, a vehicle, an electrical or mechanical device, an inanimate object, or any other trackable item.

Multiple reporting sources 208 include such as, but not limited to, permanently installed devices 210, asset installable/removable devices 215, portable computing devices 220, personal digital assistants 225, smart phones 230, mobile phones 235, human intelligence (HumInt) 240, Global Navigation Satellite System (GNSS) survey rover 245 and machine control system 247 installations. While multiple reporting sources 208 are shown, the list is exemplary. It should be appreciated that reporting sources 208 may include any number of reporting sources and reporting source methods including audio, video, text, Braille, codes, passwords, and the like. For example, reporting sources 208 may include electronic devices, GNSS enabled devices, machine controls, video enabled devices (e.g., camera enabled handheld devices such as mobile phones with cameras/cameras, PDAs with cameras/cameras, belt watches with cameras/video cameras, etc.), video cameras, webcams, etc.), human resources, monitored assets, other assets, etc. In one embodiment, any or all of the reporting sources 208 can provide asset information including, but not limited to, location information, operational information, and condition information.

装置(两者均由Trimble NavigationLimited提供)、射频识别器(RFID)、全球导航卫星系统(GNSS)接收器、提供视频速度的视频装置，等等。而且，每个报告源208可以包括诸如位置固定、摄影、发文本消息、发语音消息、发数据消息、射频识别标签读取等能力。此外，在一个实施方案中，任一个或所有的报告源208能够进行资产操作监控。例如，任一个或所有的报告源208能够与资产连接以监控包括但不限于J总线、CAN总线、与资产耦合的处理器、诊断评估器、发动机微处理器、里程指示器、速度计、转速表、油压指示器、轮速指示器、液压指示器、发动机时间监控器、点火开关电源等方面。In one embodiment, asset installable/removable device 215 may be a TrimTrac ^™ device,

devices (both supplied by Trimble Navigation Limited), radio frequency identifiers (RFID), global navigation satellite system (GNSS) receivers, video devices providing video speed, etc. Also, each reporting source 208 may include capabilities such as location fixation, photography, text messaging, voice messaging, data messaging, radio frequency identification tag reading, and the like. Additionally, in one embodiment, any or all of the reporting sources 208 are capable of asset operation monitoring. For example, any or all of the reporting sources 208 can be connected to the asset to monitor including, but not limited to, J-bus, CAN bus, processor coupled to the asset, diagnostic evaluator, engine microprocessor, mileage indicator, speedometer, tachometer Gauge, oil pressure indicator, wheel speed indicator, hydraulic indicator, engine time monitor, ignition switch power supply, etc.

Referring now to FIG. 2B , a network diagram of an exemplary asset management method in accordance with another embodiment of the present invention is shown. In one embodiment, the asset management network 250 includes a database 205 and a plurality of reporting sources 208, similar in form and function to that in FIG. 2A, which are not described in detail for the sake of brevity and clarity. However, the asset management network 250 also includes an optional asset information report generator 350 and an optional asset information report 360 . Further details of the description and operation of optional asset information report generator 350 and optional asset information report 360 are provided in the discussion with respect to FIG. 3 .

Asset management network 250 also includes automatic asset assignment module 355 , automatic reporting source assignment module 356 , reporting source grouper 357 , and asset grouper 358 . Generally, these components are optional and are used to provide further organization to the asset information report 360 . For example, preferences may be selected to group multiple assets based on location, etc., such as described in more detail herein.

Basically, the automatic asset assignment module 355 is configured to assign assets to sections in the asset information report 360 . Automatic reporting source assignment module 356 is configured to assign first reporting source 208A, second reporting source 208B, and any or all other reporting sources 208 to sections in asset information report 360 . Reporting source grouper 357 is configured to group first reporting source 208A, second reporting source 208B, and any or all other reporting sources 208 into at least one source group based on location. Asset grouper 358 is configured to group at least one asset into at least one group.

asset management system

Referring now to FIG. 3 , there is shown a block diagram of an exemplary asset management system 300 in accordance with one embodiment of the present invention. In one embodiment, the asset management system 300 receives input from the first reporting source 208A and the second reporting source 208B.

Typically, the first reporting source 208A and the unrelated second reporting source 208B are selected from the set of reporting sources 208 of FIG. 2A . Additionally, the first reporting source 208A and the second reporting source 208B may be the same or different reporting sources. Also, there may be more than two different reporting sources providing information to asset management system 300 . For example, there may be three, four, seven, fifteen, or any number of different reporting sources that provide information to asset management system 300 . For purposes of brevity and clarity, this article only shows the use of two different reporting sources. In one embodiment, the reporting source input to asset management system 300 consists of asset-related information such as, but not limited to, operation, location, condition, and the like.

In one embodiment, asset management system 300 includes data receiver 330 and database 205 . Typically, data receiver 330 is a wired or wireless connection that provides a connection between asset management system 300 and an external reporting source, such as first reporting source 208A and second reporting source 208B. In one embodiment, the connection is a network connection such as a local area network (LAN) connection, a wide area network (WAN) connection, a virtual private network (VPN), a cellular network, or the like. In another embodiment, the data receiver 330 will receive information from the reporting source via a direct connection. For example, first reporting source 208A may be communicatively coupled (wired such as via a Universal Serial Bus (USB), FireWire or other data port, or wirelessly such as Bluetooth) to data receiver 330, which may receive the information directly .

The data receiver 330 then transmits (wired or wirelessly via cellular network, WiFi, etc.) the received asset information to the database 205 where information related to the asset is stored. As stated herein, database 205 may be a single database on a single computing system, or may actually consist of multiple databases on a single computing system or multiple computing systems. Also, multiple databases may be co-located or spread across multiple locations. Additionally, multiple databases can be coupled together by wire or wirelessly to form a database network in which asset information can be stored.

In one embodiment, asset management system 300 may also include an optional report generator 350 that provides optional asset information reports 360 . In general, optional report generator 350 is one of many possible methods for organizing and presenting the information stored in database 205 . For example, a user may query asset management system 300 for one or more assets. Asset management system 300 may simply provide query results to optional report generator 350 . Optional report generator 350 then generates optional asset information report 360 that includes responses to user queries. The optional asset information report 360 can be presented in a variety of ways, depending on user preferences, system requirements, and the like. For example, optional asset information report 360 may be provided in a visual format, such as paper, or a graphical user interface (GUI) displayed on a cell phone, PDA, or laptop or desktop computer system. In another embodiment, the optional asset information report 360 may be provided in an audio format, Braille, or the like.

asset management operations

Referring now to FIG. 4 , there is shown a flowchart of an exemplary asset management method in accordance with one embodiment of the present invention.

Referring now to 402 of FIG. 4 in conjunction with FIG. 3 , one embodiment receives asset-related information from a first reporting source 208A. In one embodiment, information is received into database 205 via data receiver 330 as described in detail herein. The information may be received by wired or wireless means and by a direct connection of the reporting source to the data sink 330 or over a network.

装置(两者均由Trimble Navigation Limited提供)、移动式电话、摄像装置、个人数字助理、便携式计算装置、射频识别器、全球导航卫星系统(GNSS)和人类智能(HumInt)。In one embodiment, data receiver 330 receives asset location data from first reporting source 208A. Typically, asset location data refers to geographic location information. For example, if the asset is a vehicle, location data may include, but is not limited to: whether the vehicle is on site, on the road, in the correct area of the site, etc. Typically, asset location data may be received from sources such as, but not limited to: TrimTrac ^™ devices,

devices (both provided by Trimble Navigation Limited), mobile phones, camera devices, personal digital assistants, portable computing devices, radio frequency identifiers, global navigation satellite systems (GNSS) and human intelligence (HumInt).

In another embodiment, the data receiver 330 receives asset operation data from the first reporting source 208A. Typically, asset operations data refers to actual asset operations. For example, if the asset is a vehicle, operational data could include: asset speed, mileage, hours, time elapsed since an oil change or other planned maintenance, any screeches, what the vehicle is actually doing or has done before things, and so on. Also, asset operation data may include actual or previous operation of the vehicle. Typically, asset operational data may be generated by operational monitoring devices including, but not limited to: J-bus, CAN-bus, asset processors, diagnostic evaluators, engine microprocessors, mileage indicators, speedometers, tachometers, oil pressure indicator, wheel speed indicator, hydraulic pressure indicator, engine time monitor, ignition switch power supply, and more.

Referring now to 404 of FIG. 4 in conjunction with FIG. 3 , one embodiment receives asset-related information from the second reporting source 208B. In one embodiment, information is received into database 205 via data receiver 330 as described in detail herein. The information may be received by wired or wireless means and by a direct connection of the reporting source to the data sink 330 or over a network.

装置(两者均由Trimble Navigation Limited提供)、移动式电话、摄像装置、个人数字助理、便携式计算装置、射频识别器(RFID)、全球导航卫星系统(GNSS)和人类智能(HumInt)。In one embodiment, data receiver 330 receives asset location data from second reporting source 208B. Typically, asset location data refers to geographic location information. For example, if the asset is a vehicle, location data may include, but is not limited to: whether the vehicle is on site, on the road, in the correct area of the site, etc. Typically, asset location data may be received from sources such as, but not limited to: TrimTrac ^™ devices,

devices (both provided by Trimble Navigation Limited), mobile phones, camera devices, personal digital assistants, portable computing devices, radio frequency identifiers (RFID), global navigation satellite systems (GNSS) and human intelligence (HumInt).

In another embodiment, the data receiver 330 receives asset operation data from the second reporting source 208B. Typically, asset operations data refers to actual asset operations. For example, if the asset is a vehicle, operational data could include: asset speed, mileage, hours, time elapsed since an oil change or other planned maintenance, any screeches, what the vehicle is actually doing or has done before things, and so on. Also, asset operation data may include actual or previous operation of the vehicle. Typically, asset operational data may be generated by operational monitoring devices including but not limited to: J-bus, asset processor, diagnostic evaluator, engine microprocessor, mileage indicator, speedometer, tachometer, oil pressure indicator , wheel speed indicator, hydraulic pressure indicator, engine time monitor, ignition switch power supply, etc.

Also, as described herein, although two reporting sources 208 are shown, the present invention is also adapted to receive information from more than two reporting sources 208 (as shown in FIG. 2A ). For example, in one embodiment, data receiver 330 may receive asset information from multiple sources, such as any or all of sources 210-240.

Referring now to 406 of FIG. 4 and FIG. 3 , one embodiment augments database 205 with information from first reporting source 208A and second reporting source 208B to enable asset-related information to be determined from database 205 . In one embodiment, database 205 provides real-time location and/or operational monitoring capabilities of assets. In another embodiment, database 205 provides near real-time location and operation monitoring capabilities of assets.

That is, any or all of the reporting sources 208 that provide information about an asset may be configured to provide information continuously, regularly to provide scheduled information updates, or to provide information updates only when requested by a user. For example, the reporting source may be a PDA 225 incorporating a Global Navigation Satellite System (GNSS) receiver with the capability of positioning based on signals from Galileo, GPS, Glonass, WAAS Wide Area Augmentation Service, Egnos, etc. The GNSS PDA225 provides continuous location information updates to the database. This is important if the asset changes location on a regular basis, or if it is important to track the movement of the asset. For example, assets may include things such as but not limited to tracking concrete mix delivery vehicles or loads of concrete in delivery vehicles, armored vehicles, vehicles that make a lot of movement, and the like. In the same way, any information related to an asset may be continuously updated, and for the sake of brevity and clarity, the use of location information is provided here as an example only.

However, if the actions of the asset do not require constant updates, the information may not be continuously provided to the database 205 . Using the location instance again, if the assets are located in the same area, e.g., the asset is broken, not in use, pending maintenance, etc., then location information can only be provided during the scheduled update time period. For example, in the morning, the location of the asset can be checked, and then checked again in the evening, or only once a day, or only once a week, etc. Additionally, asset information can be adjusted based on the condition of the asset. That is, asset information can only be updated periodically if the asset is not in use. However, the information may be updated on a more regular basis or even continuously as the asset operates.

Additionally, in one embodiment, asset information is presented in the form of an asset information report 360 generated from data in the database 205 . In one embodiment, the data presented in the asset information report 360 is a combination of all information received from each reporting source 208 related to the asset. However, in another embodiment, the data presented in the asset information report 360 is a combination of only a portion of the asset-related information received from any or all of the reporting sources 208 .

For example, database 205 may have redundant information about assets from multiple reporting sources 208 . That is, more than one reporting source 208 may provide asset location information. In one embodiment, when generating the asset information report 360, the report generator 350 may use all the information about the asset in the database, including redundant information. However, in another embodiment, report generator 350 may remove redundant information prior to generating asset information report 360 to reduce bandwidth, improve report clarity, and the like. In yet another embodiment, redundant information may be removed at the database level to manage the size of the database 205 .

Also, in one embodiment, asset information report 360 may be presented on a GUI, on paper, may be provided audibly, may be provided digitally to another database or application software, or may be provided in another user-selected format. For example, for users during periods such as when asset information reports are being provided over a communication network, or for visually impaired users, or for users who cannot view visual asset information reports for operational/security reasons, the asset information reports may Provided to the user by means other than visual format.

Asset Information Report

Referring now to FIG. 5, an exemplary GUI version of an asset information report 360 in accordance with one embodiment of the present invention is shown. In one embodiment, property information report 360 includes property 540 , property column 510 , information source column 508 , map section 520 , and user toolbar section 530 . In general, the user toolbar section 530 provides a way for the user to interact with the asset information report 360 .

In one embodiment, asset 540 is automatically assigned to asset column 510 in database 205 , which can be further viewed in asset information report 360 . Also, one embodiment automatically assigns the first reporting source 208A and the second reporting source 208B to the information source column 508 of the asset information report 360 . In yet another embodiment, icons for the first reporting source 208A and the second reporting source 208B are automatically provided on the asset information report 360 . For example, the icons are based on at least one characteristic of the first reporting source 208A and the second reporting source 208B.

The asset information report 360 also provides a grouping capability for grouping the first reporting source 208A and the second reporting source 208B into at least one group in the asset information report 360 . In one embodiment, the grouping of sources providing asset location information is organized according to a grouping method such as, but not limited to, the location of the first reporting source 208A and the second reporting source 208B, e.g., same job site, same fence Location, etc.; type of first reporting source 208A and second reporting source 208B, such as GNSS 225, laptop computer 220, etc.; assigned area of first reporting source 208A and second reporting source 208B, such as same workplace, same location Fence locations, etc.; users assigned to the first reporting source 208A and the second reporting source 208B, companies providing the first reporting source 208A and the second reporting source 208B, companies using the first reporting source 208A and the second reporting source 208B, etc.

In another embodiment, the asset information report 360 provides a grouping capability for grouping multiple assets into at least one group in the asset information report 360 . In one embodiment, the grouping of the plurality of assets is selected from a grouping method such as, but not limited to, the location of the asset, the type of asset, the area in which the asset is allocated, the user assigned to the asset, the company providing the asset, and the use of the asset. company of.

Additionally, when the asset information report 360 is provided on the GUI, the map image 520 may also be provided automatically. In one embodiment, map image 520 is a satellite image. In another embodiment, the map image 520 is selected from image types such as but not limited to: terrain images, road map images, hybrid images, site designs, computer-aided design (CAD) files, geographic information system (GIS) maps, etc. Additionally, in one embodiment, a user-adjustable ground fence 550 may be positioned over portions of the map image 520 . In general, ground fence 550 is a user-selectable boundary that can be drawn or placed on map image 520 .

For example, if the user is focused on an area of interest, the user can selectively mark the area of interest on the map image 520 by drawing a border around the area. Report generator 350 will then update asset information report 360 to display the boundary line and identify the coordinates of the boundary line as ground fence 550 . The ground fence 550 itself can then be used as a virtual fence. That is, if the asset 540 is within the ground fence 550, the asset 540 information may be configured such that when the asset 540 leaves the area defined by the ground fence 550, some type of alarm or message will be generated.

Additionally, in one embodiment, an icon (or other type of identification such as name, capacity, etc.) for the asset 540 may be automatically provided in the asset information report 360 . Wherein, the icon is based on at least one asset 540 characteristic received by at least one of the first reporting source 208A and the second reporting source 208B. For example, the asset is a 5 ton truck and the reporting source 208A is reporting information received from a diagnostic system such as the J-bus. Portions of the asset information report may include a vehicle identification (VIN) number or other identifying characteristic associated with the asset. When information is retrieved from database 205 by report generator 350 and provided on asset information report 360, the information will automatically become an asset identifier. In one embodiment, the information is converted directly into an identifier, such as if the diagnostic system defines itself as a system for 5 ton trucks. However, in another embodiment, the report generator 350 may identify the VIN number (or other identifier) and access another database, such as the Internet, and search the VIN number to determine the type of asset. Then, the report generator 350 may output the identity description in the asset information report 360 or may further access an icon database (such as a local database, the Internet, etc.) and match the asset's description with the icon. For example, describing "5 ton truck" may result in an icon for a 5 ton truck or just a large truck. That is, the description and icon can match exactly, or the icon can only be an approximation. Also, the asset identification description may or may not include an asset icon, depending on user preference.

As stated herein, in one embodiment, asset information report 360 may not contain information about every asset stored in database 205 or even every piece of information about a particular asset stored in database 205 . For example, users may have different levels of access to database 205 and thus may receive asset information reports 360 that are limited in scope based on the user's level of access. Although a user may have database restrictions within any format of the asset information report 360 , restrictions for specific user access are further described in connection with FIG. 6 .

Referring now to FIG. 6 , there is shown a block diagram of an exemplary printable format 600 of an asset information report 360 generated by the asset management system 300 in accordance with one embodiment of the present invention. In one embodiment, asset information report 600 includes asset type 601 , location 602 , operation 603 , planned maintenance 604 , and other 605 . In the asset information report 600, three assets are shown. However, the number of assets illustrated and the asset information provided are exemplary only. That is, the configuration of the asset information report 600 is only one of many possible report configurations and is provided herein for the purposes of brevity and clarity only.

Also, as stated herein, the asset information report 600 may include duplicate data from multiple information sources 208, or the asset information report 600 may be condensed to contain only information relevant to selected information sources 208, providing only non-redundant information, etc.

In general, asset information reports 600 are used herein to illustrate access and configuration issues that asset management system 300 may use. For example, in one embodiment, the complete database of asset information 205 includes five assets (e.g., assets 540A-540E) and five types of information (asset type 601, location 602, operational 603, planned maintenance 604, and other 605 ). Thus, a complete asset information report that includes all data within database 205 looks similar to asset information report 600 . However, asset information report 600 most likely contains less than all of the asset information in database 205 .

Thus, if each asset in database 205 is under the control of a single user, user's asset information report 600 may contain each asset and any or all user-selected information related to the asset. However, if each asset in database 205 is not under the control of a single user, each user's asset information report may only contain the portion of asset information report 600 illustrated.

For example, a rental company may have five assets ( 540A- 540E ) located in the database and may utilize the asset information report 600 to track asset location 602 , operation 603 , planned maintenance 604 and others 605 . However, the leasing company may reduce its own access to the database 205 and allow the lessee limited access to the database 205 when the asset is leased out. For example, the leasing company leases out asset 540B. The leasing company may then restrict its access to the asset's location 602 for privacy reasons. In other words, the rental company may establish a ground fence that reduces the location 602 information to within the zone and outside the zone. Meanwhile, the leasing company can continue to monitor asset operations 603 and planned maintenance 604 .

In addition, the renter may receive limited access to the leasing company database 205, and thus receive the asset information report 600 containing any or all information related to the particular leased asset (eg, 540B). For example, a renter can access location 602 and operation 603 information, but cannot view planned maintenance information 604 . In another embodiment, the renter only has access to parts of the information such as whether the machine is running, but not the speed at which the machine is traveling.

By utilizing the asset information report 600 segmentation, restriction, and access management methods described herein, the present invention allows asset-related information to be provided to as few or as many users as desired. In addition, the present invention provides any or all users with different levels of information access based on user preferences or other information management schemes.

Thus, embodiments of the present invention provide automated asset management systems and methods. Embodiments further provide automated asset management systems and methods that include asset location information. Embodiments further provide automated asset management systems and methods that include asset operational information. Embodiments further provide asset management systems and methods that are user configurable and displayable in a variety of formats and configurations based on user and system administrator preferences. For example, display results may be provided at a user-selectable refresh rate, at a system-selected refresh rate, based on a ranking method, and the like.

Part II: Enhanced Asset Management

Enhanced Asset Management System

An enhanced asset information system is an asset information system that further improves the efficiency, simplicity, or availability of asset information. It may include making additions or modifications to the asset information system 300 that allow customizing and/or formatting of asset information reports for or in relation to customer applications that exist outside of the asset information system Application coupling.

Provides asset management information to customer applications. Referring now to FIG. 7, there is shown an exemplary enhanced asset management system 700 communicatively coupled with a customer application 710 in accordance with one embodiment of the present invention. Asset management system 700 is composed of data receiver 330 , database 205 and asset information report generator 750 .

Generally, data receiver 330 is configured to receive asset-related information from multiple reporting sources, such as sources 208A and 208B. The data receiver 330 reports the asset information to the database 205, and then uses the first portion of the asset-related information from the first reporting source 208A, the second portion of the asset-related information from the second reporting source 208B, and thereby Database 205 is augmented by analogy with other reporting sources 208 that report information related to assets. Also, database 205 may similarly receive and maintain information for multiple assets. The specific functions and operations of the database 330 and the database 205 have been described above, and for the purpose of brevity and clarity, no further description will be given here unless any differences or features not previously described need to be identified.

The asset information report generator 750 operates in the same manner and possesses the same qualities as the optional asset information report generator 350 previously described. Accordingly, similar to asset information report generator 350 , asset information report generator 750 is configured to be communicatively coupled with database 205 to generate asset information report 360 from asset information data provided from database 205 . As previously described, asset information report 360 includes data, such as operational data or location data for at least one asset. However, as represented in the embodiment of asset management system 700, asset information report generator 750 is additionally configured to optionally communicate with customer application 710 (or multiple customer applications (710a, 710b . . . 710n)) Coupling for providing asset information reports 360 from database 205 to customer applications. Thus, an embodiment of asset management system 700 is configured to provide one or more asset information reports 360 to one or more customer applications 710 in addition to the previously described techniques of providing asset information via reports 360 .

The customer applications 710 discussed herein are software applications for reporting, managing, viewing, processing or manipulating asset information. For example, customer applications are applications such as, but not limited to, spreadsheet applications, text processing applications, database applications, accounting applications, project management applications, payroll applications, billing applications, rental asset management applications, inventory applications Software applications for programs, database files, computer servers, etc. Typically, customers have one or more internal processes residing on customer applications 710 that can benefit from the use of asset management information maintained in database 205 . The foregoing description of the asset management report 360 describes asset management information provided by the asset information report generator 350 in a format such as a printed report or a graphical user interface. In addition to these report formats, asset information report generator 750 is configured to provide asset information report 360 from database 205 to customer application 710 in an electronic format compatible with the use of customer application 710 .

FIG. 8 is a flowchart 800 of an exemplary method for providing asset management information to a customer application 710 in accordance with one embodiment of the present invention. In FIG. 8, elements 402, 404, and 406 have been described above, and are not described here again for the sake of brevity and clarity. Instead, reference is made to the previous descriptions of these flowchart elements.

Referring now to element 808 of FIG. 8 and FIG. 7 , one embodiment provides asset information reports 360 from database 205 to customer application 710 . In situations where customers using asset management system 700 desire to use asset management information in their own customer applications 710, communicatively coupling asset management information from database 205 to customer applications 710 provides benefits in many instances. efficiency gain. For example, communicatively coupling asset information report 360 with customer application 710, directly or indirectly, provides a significant time savings when printing or viewing report 360 and then manually re-entering information from the report into customer application 710 and labor reduction. This can reduce or eliminate processing bottlenecks often associated with manually entering data into customer applications. Reducing or eliminating this data entry bottleneck provides useful real-time or near-real-time access to asset information within customer applications 710 without delays of hours or even days in accessing asset information as may be encountered with current data entry methods .

Consider the example of an equipment rental company that uses a database to track maintenance requirements for construction equipment assets and other leased assets leased by the company. For the purposes of this example, the rental company's maintenance database can be considered the customer application 710 . The printed asset information report 600 shown in FIG. 6 shows the data fields for the leased asset computer 504A, truck 540B, and jack 540C (type information 601, location information 602, operation information 603, planned maintenance information 604, and other information 605) . In this example, all of this asset information is used in the rental company's maintenance database. Rather than printing out the report and then manually retyping the information from the report into the maintenance database, the asset information report generator 750 allows information to be coupled, directly or indirectly, with minimal effort on the part of the operator of the asset management system 700 to in the customer application.

For example, in one embodiment, a user of asset information report generator 750 selects a database file type (or another file type, depending on customer application 710 ) as the output format for asset information report 360 . In one embodiment, asset information report generator 750 sends a desired asset information query to database 205 . In one embodiment, the query indicates that the customer application 710 whose data will be formatted is a particular type of maintenance database (or some other type of customer application 710), or that the asset information report 360 is delivered to the customer application 710 the correct electronic file type, such as a database file. In one embodiment, database 205 responds to the query by supplying asset information report 360 formatted in an electronic file type such as a database file readable and usable by customer application 710 (maintenance database in this example). The asset information report generator 750 then stores the asset information report 360 as an electronic file or forwards it to the customer application 710, depending on the user's choice.

In another embodiment, asset information report generator 750 sends a query for asset information to database 205 . In one embodiment, such as in the case of custom reporting, the query is generated by a custom reporting module (described below) accessed by information report generator 750 . The asset information report generator 750 then formats the asset information received from the database 205 into an electronic file-type asset information report 360 readable by the customer application 710 (maintenance database in this example). In one embodiment, asset information report generator 750 references instructions in the custom reports module to format asset information report 360 into the correct electronic file format for customer application 710 . In one embodiment, the asset information report 360 is forwarded to the customer application 710 after the asset information report 360 is properly formatted, such as a database file. In another embodiment, asset information generator 750 stores formatted asset information report 360 as an electronic file.

The storage asset information report 360 allows the user to select the manner in which the electronic file is transferred to the customer application 710, such as by: transferring the file to a portable medium (disk, flash drive, etc.), and by manually copying the file to the computer system or the customer The network in which the application 710 is running; emailing the file to an account accessible from the computer system or network where the customer application 710 is located; via a wired or wireless coupling between the asset management system 700 and the customer application 710 (such as Bluetooth, Intranet, Local Area Network, Wide Area Network, Internet, wireless network, cellular telephone network, or other similar wired or wireless information transfer means used to transfer information) to access stored files manually or automatically.

Although flowchart 800 describes a method for reporting on a single asset, it should be understood that in some embodiments, database 205 receives information about multiple assets. In such an embodiment, providing the asset information report 360 from the database 205 may include receiving an asset information query related to the grouping of the plurality of assets. Many such groupings are possible, such as, for example, groupings based on factors such as: time period of operation of the asset (e.g., day, date, time of day, time range, etc.); location of operation of the asset (e.g., within a particular fence); the type of asset (truck, bulldozer, computer, etc.); the area assigned to the asset (e.g., a fenced area around a construction site); the users assigned to the asset (e.g., specific workers); entities that own or operate assets). As previously described, the asset information report generator 750 then stores or forwards the asset information received in response to the query. In some embodiments, asset information report generator 750 formats as needed to format asset information report 360 into the correct electronic format for customer application 710 designated as the recipient of asset information 360, as previously described. file type.

Accordingly, asset information report 360 usable by customer application 710 may be coupled directly or indirectly to customer application 710 . This saves time, improves the company's operational efficiency, and reduces data errors as compared to manually entering information from asset information reports into customer application 710 .

Customized asset information report

In some instances, the standard asset information report 360 generated by the asset information report generator 750 may contain more or less information than is required by a particular customer application 710 . Likewise, the standard asset information report 360 generated by the asset information report generator 750 may arrange asset information in a manner that the customer does not like or that is incompatible or inconsistent with the arrangement of asset information used within the customer application 710 . Also, in some instances, asset information report generator 750 may not be designed to provide asset information report 360 in a desired electronic file format that is compatible with a particular customer application 710 . In these instances, it may be desirable to have customized asset information reports 360 . In one embodiment, the ability to generate customized asset information reports 360 is provided by configuring asset information report generator 750 to recognize and utilize one or more plug-in custom report generator modules.

Referring now to FIG. 9 , an expanded block diagram of an asset information report generator 750 for use with an exemplary asset management system 700 is shown, in accordance with one embodiment of the present invention. As shown in FIG. 9 , the asset information report generator 750 is composed of an automatic asset allocation module 355 , an automatic report source allocation module 356 , a report source grouper 357 and an asset grouper 358 , all of which have been described above. The embodiment of the asset information report generator 750 shown in FIG. 9 also includes a first custom report module 959A and a second custom report module 959B. It should be understood that fewer or more custom reporting modules may be included in other embodiments of the asset information report generator 750, depending on the number of customized asset information reports that the user desires to generate.

FIG. 10 is a flowchart 1000 of an exemplary method for providing customized asset management information in accordance with one embodiment of the invention. In FIG. 10 , elements 402 , 404 and 406 have been described above and will not be described here again for the sake of brevity and clarity. Instead, reference is made to the previous descriptions of these flowchart elements.

Referring now to 1008 of FIG. 10 and FIGS. 7 and 9 , one embodiment receives a first customized asset information database query from a first customized reporting module 959A. For example, in one embodiment, the first customized reporting module 959A sends a customized asset information query to the database 205 via the asset information report generator 750 to query the customized asset information report 360 for information. In one embodiment, this is a customized query for specific information related to a specific asset or specific grouping of assets. In one embodiment, the query is a standard or customized query of the asset, and the response to the query will be formatted in a manner customized according to the instructions provided by the first custom reporting module 959A.

Referring now to 1010 of FIG. 10 and FIGS. 7 and 9 , one embodiment provides the asset information report 360 in a first format specified by the first custom reporting module 959A. In one embodiment, the first custom reporting module 959A formats information received from the database 205 in response to a query. For example, information can be formatted into an arrangement of customized asset information reports 360 and then output as electronic files, printed reports, graphical user interfaces. Such reports may also be saved, exported or provided to customer applications 710.

In one embodiment, providing asset information report 360 includes providing asset information report 360 in a format of a customized electronic file type usable by customer application 710 . This is especially useful when generating asset information reports 360 for a particular customer application 710 is not supported by asset information report generator 750 . For example, an electronic file type may be a file type used by customer applications 710 such as, but not limited to, spreadsheet applications, text processing applications, database applications, accounting applications, project management applications, payroll applications, Billing applications, rental asset management applications, inventory applications, and more.

In one embodiment, providing the asset information report 360 includes providing the asset information report 360 in which the asset information is displayed in a customized configuration, such as a customized visual configuration. This may include a visual presentation of icons overlaid on the map, a special arrangement of data rows and columns, or some other customized visual arrangement of asset information specified by a custom reporting module such as custom reporting module 959A. In one embodiment, providing an asset information report includes providing an asset information report with a particular set of asset information specified by the first custom reporting module 959A. This is useful, for example, when the standard property information report 360 available from the property information report generator 750 contains too much information or not enough information for the customer.

Referring now to FIG. 11 , there is shown a diagram of an exemplary printable format 1100 of a custom asset information report 360 generated by the asset management system 700 in accordance with one embodiment of the present invention. As shown in Figure 11, an asset information report with a customized title 1110 "Weekly Truck Usage Report" has been generated by the customized reporting module 959A. This report has been formatted with information from a custom query of asset information related to asset 540B trucks. The information is arranged in a customized configuration of rows and columns, where each row represents asset 540B and each column represents specific asset information related to asset 540B. Column 601 represents the asset type. Column 1104 represents the day of the work week. Column 1106 represents the calendar date associated with a particular day of the work week. Finally, column 1108 represents the total number of hours that asset 540B was used during a particular day and date.

For example, the custom printable format 1100 is used by the payroll department to determine whether the number of hours the asset has actually been in operation corresponds to the asset operator's automatic clock entry. In this example, the employee is a truck operator who wears an RFID name badge that triggers a clock entry while the employee's name badge is in the cab of truck 540B. If the clock entry shows that the employee (or more specifically his name badge) is in the cab of truck 540B for eight hours each workday (Monday-Friday), then it is easy to determine that at the employee's clock time and asset 540B is on Friday There was a discrepancy between the number of hours operated on August 18 (5.7). Investigations indicated that the employee may have sat idle for more than two hours, leaving his name badge in a non-operating vehicle, or that Truck 540B was not operating as efficiently as possible during the workday. Additionally, in one embodiment, if eight hours of operating time is a standard amount of expected operating time, block 1120 may be automatically flagged or highlighted to indicate a large deviation from the expected operating time for asset 540B.

型操作环境实现的一个实施方案中，每个定制报告模块实现为存储在可由资产信息报告生成器750自动访问的目录中的动态链接库(DLL)文件。为了编程的简易性，在一个实施方案中，使用.NET编程语言来实现资产信息报告生成器750。这允许用.NET兼容语言来编写定制报告模块，这将有利于通过功能、所提供的用户接口以及资产信息报告生成器750的其它模块进行流线型配合操作。在这种实施方案中，用.NET编程语言编写的定制报告模块可以存储在可由资产信息报告生成器750访问的目录中，例如存储为DLL文件。A custom reporting module, such as custom reporting module 959A, can be implemented in a variety of ways. For example, in one embodiment, custom reporting module 959A includes files accessed by asset information report generator 750 . In one embodiment, this file may contain a set of pre-constructed database queries for sending to database 205 . These queries may be issued manually by a user or automatically, such as at startup or at predetermined time intervals. In Asset Information Report Generator 750 with

In one embodiment implemented in a type operating environment, each custom reporting module is implemented as a dynamic link library (DLL) file stored in a directory that is automatically accessible by the asset information report generator 750. For ease of programming, in one embodiment, the asset information report generator 750 is implemented using the .NET programming language. This allows custom reporting modules to be written in a .NET compatible language, which facilitates a streamlined operation through the functionality, user interface provided, and other modules of the Asset Information Report Generator 750 . In such an embodiment, a custom reporting module written in the .NET programming language may be stored in a directory accessible by the asset information report generator 750, eg, as a DLL file.

If additional customized asset information reports 360 are desired, additional custom report modules (959B...959n) are added to the asset information report generator 750 to facilitate generation of the desired reports. For example, in FIG. 9, the asset information report generator 750 is shown configured with a second custom reporting module 959B. In one embodiment, the second customized reporting module 959B automatically sends a second customized asset information query to the database 205 for the purpose of generating the second customized asset information report 360 . A second asset information report is then provided by asset information report generator 750 in a second format specified by second custom report module 959B. Additional custom reporting modules (959B...959n) are implemented and operate in a manner consistent with the above-described implementation and operation of custom reporting module 959A.

By establishing the ability to recognize and use custom reporting modules such as custom reporting module 959A, multiple parties are allowed to implement plug-in custom reporting modules for asset information report generator 750 . For example, in one embodiment, the original manufacturer of asset management system 700 can create custom reporting module 959A for use by one or more customers. This is useful for upgrading or tailoring the asset management system 750 to the needs of a particular customer. Likewise, technology-savvy customers can create their own custom reporting modules 959A. Additionally, the manufacturer, customer, or both may have the flexibility to hire independent contractors to create custom reporting modules 959A to meet specific needs.

Thus, embodiments of the present invention provide enhanced asset management systems and methods. Embodiments further provide automated methods for customizing reporting of asset information both visually and electronically. Embodiments also provide an automated method of providing asset information reporting for customer software applications running independently of the enhanced management system. Additionally, methods and systems are provided for storing electronic files formatted for use with customer applications or for providing such formatted files to customer applications either manually or automatically.

SECTION III: PROVIDING CONDITION INFORMATION RELATED TO THE ASSET

overview

Referring to FIG. 3 , asset-related information from more than one reporting source 208A and 208B may be received by asset management system 300 and stored in database 205 . According to one embodiment, asset management system 300 may be provided by a leasing company. According to one embodiment, construction company employees may use client computers to request and display information stored in database 205 . For example, they may use a client computer to display a visual representation that includes a schematic or graphical image of the construction site and the assets that are being used on the construction site.

According to one embodiment, the asset information may include condition information received from at least one reporting source 208A or 208B related to the asset. Examples of status information include alerts and warnings. According to one embodiment, condition information related to an asset may be provided to a client, for example, for the purpose of displaying a visual representation of the asset condition information.

asset management system

Figure 12 depicts an asset management system in communication with clients, according to one embodiment. The blocks representing features in FIG. 12 may vary from the illustrated arrangement and can implement additional or fewer features than described herein. Furthermore, the features represented by the blocks in FIG. 12 can be combined in various ways. System 1200 may be implemented using software, hardware, firmware, or a combination thereof.

FIG. 12 depicts client 1210 , display 1220 , asset management system 1230 and database 1240 . The asset management system 1230 includes a multi-reporter asset information store 1232 and a multi-reporter asset information provider 1234 . Database 1240 includes asset-related information 1250 and asset condition information 1252 .

Asset management system 1230 is capable of receiving asset-related information from more than one reporting source 208 . According to one embodiment, information related to assets is stored in database 1240 resulting in stored information 1250 . Asset-related information 1250 includes condition information about asset 1252, according to one embodiment. According to one embodiment, the condition information 1252 related to the asset may be provided, for example, to the client 1210 for the purpose of displaying a visual representation (VirtRep) 1222 of the asset condition information 1252 .

assets

Examples of assets include, but are not limited to, motor graders, graders, bulldozers, saws, chip trucks, excavators, pavers, concrete mix trucks, supply trucks, cranes, implements, service trucks, compressors, etc. Although many descriptions of the embodiments provided herein refer to construction assets, the various embodiments are also applicable to other types of assets. Refer to Section I, among many other sections, for more asset-related information.

report source

2A, examples of reporting sources 208 include, but are not limited to, permanently installed devices 210, asset installable/removable devices 215, portable computing devices 220, personal digital assistants (PDAs) 225, smartphones 230, mobile phones 235, and manual Smart 240. Refer to the discussion of reporting sources 208 in Section I for more information on reporting sources.

information about assets

According to one embodiment, asset-related information is received from a first reporting source and asset-related information is also received from a second reporting source. Information received from two reporting sources may be stored in database 1240 resulting in stored information 1250 . Refer to the description of step 406 (FIG. 4) for more information on augmenting the database.

According to one embodiment, information 1250 is asset location data. Examples of asset location data include, but are not limited to: whether the vehicle is on site, on the road, or in the correct area of the site. According to another embodiment, the information 1250 is asset operation data. Examples of asset operational data include, but are not limited to: the speed at which the asset is being driven, the time elapsed since the last oil change or other planned maintenance was performed on the asset, any indications of possible failure of the asset, and the activities the vehicle is currently or has previously been involved in . Screeching sounds may be an indication of a possible asset failure.

Information 1250 may be used to determine: how much the asset has been used, where the asset is located, whether the asset is being used properly, whether the asset has left a designated area such as delimited by a ground fence, when the asset needs maintenance, what service truck is best suited to perform the maintenance, etc. Refer to the description of steps 402 and 404 of Part I (FIG. 4) for more information on "Information Related to Assets".

status information

According to one embodiment, asset information 1250 may include condition information 1252 received from at least one reporting source 208A or 208B related to the asset. Examples of status information 1252 include alerts and warnings.

According to one embodiment, the condition information 1252 related to the asset may be provided to the client 1210 for the purpose of displaying a visual representation 1222 of the asset condition information 1252, for example. Asset management system 1230 may provide status information 1252 to client 1210 in the form of a notification. Client 1210 may request status information 1250 from asset management system 1230 by, for example, periodically polling asset management system 1230 in real time.

Examples of condition information 1252 are alarms and warnings, eg, an asset may have moved outside the ground fence, an asset may require maintenance or is close to requiring maintenance, an asset may be being used improperly, or an asset may be in a dangerous situation. Another example of condition information is related to productivity, such as a warning that the motor grader only graded 1000 feet when it should have graded 2000 feet. Yet another example of condition information relates to whether an asset is being used outside of its design or tolerances. These are just a few examples of status information. Embodiments of the present invention can be used with many different types of status information that an owner or user of an asset may need to know.

According to one embodiment, asset condition information 1252 may be cleared, for example, after a person has viewed a visual representation of condition information 1222 . For example, a person using the client 1210 can clear the condition information 1252 for a particular asset from the database 1240 after he has seen the visual representation 1222 of that asset's condition information.

Visual representation of status information

The display 1220 of the client 1210 can be used to display a visual representation of the construction site and assets in use at the construction site. The visual representation of the construction site may be a map of the construction site. The visual representation of an asset can be an icon. Visual representations of assets can be positioned to indicate their corresponding locations in the construction site map. The visual representation of an asset looks similar to the asset it represents. For example, a visual representation of a service truck looks like a service truck.

According to one embodiment, the visual representation of the condition information is at least part of the visual representation of the asset. For example, a visual representation of an asset may include a visual representation of condition information for the asset.

According to one embodiment, the visual representation of an asset may change color to reveal status information 1252 related to the asset. For example, the visual representation may be red to indicate a critical state, yellow to indicate a warning, and green to display status information that is neither critical nor warning. According to one embodiment, the color of the entire visual representation may change, or the color of a portion of the visual representation may change.

According to another embodiment, status information 1252 related to an asset may be displayed by outlining a visual representation of the asset with color. According to one embodiment, an outline indicative of condition information is considered part of the visual representation of the asset. According to yet another embodiment, status information 1252 is displayed by causing visual representation 1222 to appear faintly (also referred to as "blinking"). The rate at which the visual representation 1222 "blinks" can also be used to convey status information 1252 . For example, visual representation 1222 may blink faster for higher priority status information. According to yet another embodiment, different approaches may be combined to display the visual representation 1222 of the status information 1252 . For example, an icon may turn red and flash rapidly to indicate a critical situation. According to another embodiment, the status information 1252 is displayed when the client 1210 detects that the user has positioned the cursor in close proximity to hovering over the visual representation of the asset.

Operation example of method for providing condition information related to assets

Figure 13 is a flowchart of a method for restricting access to asset management information, according to one embodiment. Although specific steps are disclosed in flowchart 1300, these steps are exemplary. That is, embodiments of the present invention are also applicable to performing other various steps or variations of the steps recited in flowchart 1300 . It should be understood that the steps in flowchart 1300 may be performed in a different order than presented, and that not all steps in flowchart 1300 may be performed.

All or part of the implementation described by flowchart 1300 may be implemented using computer readable and computer executable instructions residing in a computer usable medium of a device such as a computer system. As noted above, in one embodiment, some of the processes and steps of the present invention are implemented as a series of instructions (eg, software programs) stored in and executed by a computer-readable memory of a computer system. When executed, the instructions cause the computer system to perform the functions of the invention as described below.

In step 1310, the method begins.

In step 1320, asset-related information from the first reporting source and the second reporting source is stored in a database. For example, for assets as shown in FIGS. 8 and 10 , information can be received from first and second reporting sources 208 . For the sake of illustration, assume that the first reporting source is asset installable/removable device 215 . Device 215 may be mounted to an asset. Device 215 may be used to collect information about an asset, such as while the asset is moving around. For the sake of illustration, assume that the second reporting source is a personal digital assistant 225 (PDA). An employee of the construction company or a vendor may walk around and enter information related to the asset into the PDA 225. Thus, according to one embodiment, asset-related information may be received from more than one reporting source 208 . Refer to the subheading "Information" of Section III and the discussion of step 404 for more information related to receiving information about assets from the first and second reporting sources.

Multiple reporting source asset information storage 1232 ( FIG. 12 ) is capable of storing received information resulting in stored information 1250 . Refer to the description of step 406 of Section I (FIG. 4) for more information on storing information into a database (also referred to as augmenting the database).

For the sake of illustration, assume the asset is a bulldozer. The device 215 can periodically send location information related to the bulldozer to the asset management system 1230 (FIG. 12). The asset management system 1230 can compare the location of the bulldozer to the ground fence. For the sake of illustration, assume the bulldozer leaves the ground fence. By comparing the position of the bulldozer to the ground fence, the asset management system 1230 can determine that the bulldozer has left the ground fence. According to one embodiment, the asset condition information 1252 for the bulldozer will reflect that the bulldozer has left the ground fence.

In step 1330, status information about the asset is provided to the client. The status information may be used to display a visual representation of the status information on the client. For example, client 1210 may poll asset management system 1230 for asset status information 1252 . Client 1210 can receive status information 1252 indicating that the bulldozer has left the ground fence. Client 1210 can display visual representation 1222 of status information 1252 . For example, the bulldozer icon turns red or starts flashing rapidly. Refer to the subheading "Visual Representation of Status Information" in Part III for more information.

In step 1340, the method ends.

Part IV: Enabling Asset-Related Notifications

overview

Referring to Figure 21, a construction company 2130 typically owns a core set of assets that they use to perform work on a construction site. If the construction company 2130 needs more assets than they own, they can lease additional assets from the leasing company 2120 . The leasing company can be a seller 2122 or a non-seller 2125. Leasing companies 2120 may also own assets that they do not lease. For example, rental companies may own service vehicles that they use to maintain other assets that have been leased.

Referring to FIG. 3 , asset-related information from more than one reporting source 208A and 208B may be received by asset management system 300 and stored in database 205 . According to one embodiment, the received information is used to enable asset-related notifications to be provided to construction companies and/or leasing companies.

asset management system

Figure 14 depicts an asset management system for enabling asset-related notifications, according to one embodiment. The blocks representing features in FIG. 14 may be arranged differently than shown, and more or fewer features can be implemented than described herein. Furthermore, the features represented by the blocks in FIG. 14 may be combined in various ways. System 1400 may be implemented using software, hardware, firmware, or a combination thereof.

System 1400 depicts appliance 1410 , notification 1420 , asset management system 1430 and database 1440 . Asset management system 1430 includes multi-reporter information receiver 1432 and multi-reporter state machine holder 1434 . Database 1440 includes asset-related information 1442 and asset-related state machines 1444 .

Asset management system 1430 is capable of receiving asset-related information from more than one reporting source 208 . Information received by multiple reporting source information receiver 1432 from multiple reporting sources 208 may be stored in database 1440 resulting in stored information 1442 . According to one embodiment, the multi-reporter information receiver 1432 communicates the received information to the multi-reporter state machine maintainer 1434, which uses the received information to maintain the state machine 1444 pertaining to the asset. According to one embodiment, the state machine 1444 enables the provision of asset-related notifications 1420 .

Figure 15 is a diagram of an example of an asset-related state machine 1500, according to one embodiment. State machine 1500 (FIG. 15) is an example of state machine 1444 (FIG. 14). Referring to Figure 15, an initial state may be associated with an asset. When an event occurs, the state associated with the asset changes. For example, when event 1 occurs, the state machine 1500 of the asset transitions from the initial state to state 1 . When event 3 occurs, state machine 1500 transitions from state 1 to state 2, and so on for event 4, state 3, and state 5. However, some events do not cause transitions between states. For example, event 2 leaves the state unchanged.

Some events cause notifications to be delivered to the device. Refer to the subheading "Configuration" of Section IV in other sections for more information on events causing notifications to be delivered to devices.

According to one embodiment, the state machine and/or notifications may be stored in a database. In the event of a system failure, the stored state machine and/or notifications can be used as part of a restart and possibly post-processing.

assets

Examples of assets include, but are not limited to, motor graders, graders, bulldozers, saws, chip trucks, excavators, pavers, concrete mix trucks, supply trucks, cranes, implements, service trucks, compressors, etc. Although many descriptions of the embodiments provided herein refer to construction assets, the various embodiments are also applicable to other types of assets. Refer to Section I, among many other sections, for more asset-related information.

report source

2A, examples of reporting sources 208 include, but are not limited to, permanently installed devices 210, asset installable/removable devices 215, portable computing devices 220, personal digital assistants (PDAs) 225, smartphones 230, mobile phones 235, and manual Smart 240. Refer to the discussion of reporting sources 208 in Section I for more information on reporting sources.

information about assets

According to one embodiment, asset-related information is received from a first reporting source and asset-related information is also received from a second reporting source. Information received from two reporting sources may be stored in database 1440 resulting in stored information 1442 . Refer to the description of step 406 (FIG. 4) for more information on augmenting the database.

According to one embodiment, information 1442 is asset location data. Examples of asset location data include, but are not limited to: whether the vehicle is on site, on the road, or in the correct area of the site. According to another embodiment, the information 1442 is asset operation data. Examples of asset operational data include, but are not limited to: the speed at which the asset is being driven, the time elapsed since the last oil change or other planned maintenance was performed on the asset, any indications of possible failure of the asset, and the activities the vehicle is currently or has previously been involved in . Screeching sounds may be an indication of a possible asset failure.

Information 1442 can be used to determine: how much the asset has been used, where the asset is located, whether the asset is being used properly, whether the asset has left a designated area such as bounded by a ground fence, when the asset needs maintenance, what service truck is best suited to perform the maintenance, etc. Refer to the description of steps 402 and 404 of Part I (FIG. 4) for more information on "Information Related to Assets". Information about an asset can indicate what kind of event is happening to the asset.

status and events

As shown in Figure 15, state machine 1500 includes states and events. According to one embodiment, events are used to determine how transitions between states are made. Examples of states include: the asset is on-site (WithinSite), the asset is off-site (OutsideSite), the asset is on (IgnitionOn), the asset is moving (Moving), the asset's door is open (DoorOpen), and the asset requires maintenance (MaintenancePending) . Examples of events include: asset has entered site (EnterSite), asset has left site (LeaveSite), asset has been switched on (IgnitionOn), asset has been switched off (IgnitionOff), asset has started moving (StartedMoving), asset has stopped moving ( StoppedMoving), the door has been opened (DoorOpen), the door has been closed (DoorClosed), maintenance is due (MaintenanceDue), and maintenance has completed (MaintenanceDone).

According to one embodiment, information related to scheduling, monitoring assets, scheduling assets, cargo carried by assets, among other things, may be used to determine events and/or status.

According to one embodiment, time may be used as part of defining an event. The time may be specified in terms of time slots. Examples of using instance-qualified events include: "The scene 'Lincoln Office' was entered between 9:00 AM and 5:00 PM", and "IgnitionOn did not occur between 9:00 AM and 9:15 AM. As can be seen, the state can Reflects the timing information used as part of the event that defines the transition to that state.

The number of times a state or event occurs or is entered may be used according to one embodiment. Examples are "more than 1 SpeedingEvent on gear change" or "no PositionUpdate event in last 30 minutes".

Other examples of states and events are: "NotWithinSite 'LincolnOffice' at 5 PM", "WithinSite 'PickUpPoint' at any time between 10 AM and 10:30 AM", "IgnitionIsOn at 5 PM below", or at The event "IgnitionIsOn" does not occur anytime between 9:00 AM and 9:15 AM.

According to one embodiment, states and/or events may also be combined. For example, "MaintenanceIsPending when EnterSite 'Lincoln Office' between 9am and 5pm". Another example of a combined state and/or event is "DoorIsOpen when StartedMoving occurs".

According to one embodiment, information describing events may come from one or more reporting sources and databases located external to the asset. For example, a compressor may have been taken out of the yard, and the asset management system 300 indicates that the compressor is not ready for use, thus generating an alarm. In another example, the status of an asset may indicate that the asset is on site for a particular job, that the asset is within a 20 hour maintenance period, and that a weather service predicts a storm will hit the job site tomorrow. However, for financial reasons, it is best to do maintenance tomorrow even if a storm is forecast.

According to one embodiment, states and/or events may be combined by implementing a state machine within the state. For example, the Moving state may include an event DoorOpen state machine that specifies, among other events, a transition to the DoorOpen state. In another example, the Moving state may also include an event LeaveSite that transitions to the OutsideSite state.

According to one embodiment, a state machine may be implemented using a list. For example, a state machine 1444 for a bulldozer may have a list of what events belong to a bulldozer and which events cause transitions between particular states. According to another embodiment, the state machine 1444 may be implemented using an object-oriented design pattern called "State." For more information, refer to "Design Patterns: Elements of Reusable Object-Oriented Software" by Gamma et al., ISBN 0201-63361-2, the contents of which publication are incorporated herein.

notify

According to one embodiment, the logic associated with the state may specify that the notification 1420 be communicated to the device 1410 . For example, the state MaintenancePending may specify that a notification 1420 indicating maintenance is to be sent to the device 1410 . According to one embodiment, there are different types of notifications 1420 . Among other notifications, there are alert notifications, warning notifications, and information notifications. The alert notification may relate to the asset moving beyond the ground fence, the asset accelerating, the asset approaching a cliff, or the asset running out of fuel. Warning notifications may relate, for example, to maintenance due within a certain amount of time. Information notifications can relate to assets being at a particular location or assets being moved.

Notification 1420 may be communicated to device 1410 in the form of, for example, email, fax, or calling device 1410 . There are just a few examples of how notification 1420 may be communicated to device 1410 . Notification 1420 may include time information. For example, the notification 1420 may indicate how long the state has belonged to the asset, when the state was entered, when the state was exited, how many times the event occurred, or how many times the state was entered or exited. In a particular example, the notification 1420 may indicate that the asset has moved from location a to b within time x and y. In another example, notification 1420 may indicate that on July 16, 2006, between 9:00 am and 5:00 pm, the asset's ignition was turned on.

According to one embodiment, notification 1420 is not necessarily transmitted to device 1410 immediately upon detection. For example, an information notification may not be sent to device 1410 immediately. Information may be stored in database 1440 for a period of time. The asset management system 1430 may periodically review saved notifications and determine whether to send these notifications to the appropriate devices.

According to one embodiment, notification 1420 is communicated, for example, when the wrong type of attachment is attached to the asset. For example, a notification is communicated when a large bucket is attached to a relatively small machine that could cause damage to the machine.

configuration

A user of device 1410 may specify what asset, status or event they are interested in when receiving notification 1420 . The user may also specify what form the notification 1420 will take, such as email or calling the device 1410 . According to one embodiment, a state machine 1444 may be configured for a particular asset by specifying, among other things, what state, event, belongs to that asset. For example, the IgnitionOn state can be associated with a bulldozer, but not with the bucket the bulldozer is attached to. Thus, the state machine 1444 for a bulldozer may include an IgnitionOn state, while the state machine 1444 for a bucket may not include an IgnitionOn state.

According to one embodiment, users can interact with their device 1410 to configure what states and events for a particular asset they are interested in receiving notifications for. The appliance 1410 may communicate the configuration to the asset management system 1430 . The asset management system 1430 can utilize configurations to create a state machine 1444 . The state machine 1444 may be used to determine, among other things, what notification 1420 to send, when to send the notification 1420, and what the notification 1420 will contain.

Operational instance of the method for enabling asset-related notifications

Figure 16 is a flowchart of a method for enabling asset-related notifications, according to one embodiment. Although specific steps are disclosed in flowchart 1600, these steps are exemplary. That is, embodiments of the present invention are also adapted to perform other various steps or variations of the steps recited in flowchart 1600 . It should be understood that the steps in flowchart 1600 may be performed in an order different from that presented, and that not all steps in flowchart 1600 may be performed.

All or part of the implementation described by flowchart 1600 may be implemented using computer readable and computer executable instructions stored in a computer usable medium of a device, such as a computer system. As noted above, in one embodiment, some of the processes and steps of the present invention are implemented as a series of instructions (eg, software programs) stored in and executed by a computer-readable memory of a computer system. When executed, the instructions cause the computer system to perform the functions of the invention as described below.

In step 1610, the method begins.

In step 1620, asset-related information is received from a first reporting source and a second reporting source. The information received about the asset may indicate what kind of event is happening to the asset. For assets as shown in FIGS. 8 and 10 , information may be received from first and second reporting sources 208 . For the sake of illustration, assume that the first reporting source is asset installable/removable device 215 . Device 215 may be mounted to an asset. Device 215 may be used to collect information about an asset, such as while the asset is moving around. Additionally, device 215 may be connected to a J-bus associated with an asset, thus being able to detect, among other things, whether the asset is switched on.

For the sake of illustration, assume that the second reporting source is a personal digital assistant 225 (PDA). Construction company employees or vendors can walk around and enter asset-related information into the PDA 225. Thus, according to one embodiment, the multiple reporting source information receiver 1432 is capable of receiving asset-related information from more than one reporting source 208 . Refer to the subheading "Information" of Section III and the discussion of step 404 for more information related to receiving asset-related information from the first and second reporting sources.

Additionally, received information may be stored in database 1440 as stored information 1442 (FIG. 14). Refer to the description of step 406 of Section I (FIG. 4) for more information on receiving and storing information in a database. Storing information into a database is also known as augmenting the database.

According to one embodiment, a vehicle tracking and communication system used by the fleet management system may be used as part of communicating asset related information. For more information on vehicle tracking and communication used by fleet management systems, refer to "VEHICLE TRACKING, COMMUNICATION ANDFLEET MANAGEMENT SYSTEM," filed December 19, 1999, to Coffee et al. and assigned to Sunnyvale CA (USA) U.S. Patent No. 6,611,755 to Trimble Navigation Ltd. According to one embodiment, the PROTRAK system or the Galileo system (each of PROTRAK and Galileo, either alone or with various suffixes, are trademarks of Fleet Management Services, Inc. of Chandler, Ariz.) may be used to communicate information related to the asset. information section.

In step 1630, the asset's state machine is maintained based on the received information. When an event occurs, the state machine 1444 is used to determine whether a transition from one state to another has been made. For example, suppose an asset is located on a construction site. The asset is off and the door is closed. An operator wants to get into an asset and start using it. In the example, the state WithinSite applies until the operator enters the asset. The event that the operator opens the door causes the DoorOpen state to be entered. At this point in the example, the asset's state machine reflects the states WithinSite and DoorOpen. The operator closes the door, so the status DoorOpen no longer applies to the asset. When the events IgnitionOn and StartedMoving occur, the state machine will transition to the Moving state. At this point in the example, the states WithinSite and Moving apply to the asset.

In step 1640, the method ends.

SECTION V: RECEIVING INFORMATION RELATED TO CONSTRUCTION PROJECTS

overview

According to one embodiment, a construction company receives information related to assets such as bulldozers, backhoes, compressors as part of managing a construction project. For example, employees of a construction company may want to know where a particular asset is located, what work the asset is doing, and so on. Employees can use this information to determine, among other things, whether the asset should be moved to a different location or used in a different activity.

As described particularly in Section I, asset-related information from more than one reporting source 208A and 208B may be received by asset management system 300 and stored in database 205 . Different types of assets are used in different types of construction activities and cost different amounts. Since assets have different capabilities. Construction projects use different types of assets for different activities, which are instances of construction project objectives. Different types of reporting sources also have different capabilities and cost different amounts. According to one embodiment, different types of reporting sources are associated with different assets based on the capabilities of the asset and the goals of the construction project. According to one embodiment, the capabilities of an asset should be considered part of the "characteristics" of the asset.

assets

Examples of assets include, but are not limited to, motor graders, graders, bulldozers, saws, chip trucks, excavators, pavers, concrete mix trucks, supply trucks, cranes, implements, service trucks, compressors, etc. Although many descriptions of the embodiments provided herein refer to construction assets, the various embodiments are also applicable to other types of assets. Refer to Section I, among many other sections, for more asset-related information.

Asset Characteristics and Construction Project Objectives

比RFID标签型报告源相对更加昂贵。TrimTrac^TM和可安装的报告源(MRS)1800的成本介于二者之间。建筑项目可涉及一个或多个施工现场。Examples of asset characteristics include, among other things: the cost of the asset, the mobility of the asset, the amount of information conveyed about the asset, the ability of the asset to provide power to a reporting source, the size of the asset, the accuracy with which asset location information can be provided, and the timeliness of providing information related to the asset. Examples of construction project goals include, among other things: how the asset will be used in the construction project, the amount of information that the asset management system wants to receive to manage the asset, the timeliness of the information that the asset management system wants to manage the asset, in order to manage the asset The location accuracy of assets required by the management system. Another example of a construction project objective involves reporting the relative cost of a source compared to the relative cost of an asset. For example, the more expensive an asset is, the more impartial it is to associate a relatively expensive reporting source with that asset. For example, the more powerful and better capable a reporting source is, the more expensive the reporting source is.

Relatively more expensive than RFID tag type reporting sources. TrimTrac ^™ and Installable Reporting Source (MRS) 1800 cost in between. A construction project may involve one or more construction sites.

report source

2A, examples of reporting sources 208 include, but are not limited to, permanently installed devices 210, asset installable/removable devices 215, portable computing devices 220, personal digital assistants (PDAs) 225, smart phones 230, mobile phones 235, and Artificial Intelligence 240. Refer to the discussion of reporting sources 208 in Section I for more information on reporting sources. An example of an asset installable/removable device 215 is TrimTrac ^™ , an installable reporting source (FIG. 18), and an RFID tag-based reporting source.

For more information on TrimTrac ^™ , see Nichols et al., "Method and System For Controlling A Valuable Movable Item," Attorney Docket No. TRMB-1319.CIP4, filed September 28, 2004, assigned to this Assignee of the invention to U.S. Patent Application Serial No. 10/952,607 and by reference to Workman et al., entitled "A portable Motion-Activated Position Reporting Device," Attorney Docket No. TRMB, filed March 31, 2005 - US Patent Application Serial No. 11/076,923, 1319.CIP7, assigned to the assignee of the present invention.

通常具有恒定电源并且能够在相对大的距离内频繁地传达相对大量的资产信息。RFID标签型报告源不具有电源并且能够在相对短的距离内传达相对少量的资产信息，诸如标识符。通常，报告源的能力越是好，就越是昂贵。因此，将昂贵的报告源与相对廉价的资产相关联不具有好的商业意义。根据一个实施方案，通过基于资产的特性和建筑项目的目标将不同类型的报告源与不同的资产相关联，解决了其它事项中的该担忧。Different types of reporting sources have different capabilities. For example,

Often has a constant power source and is capable of frequently communicating a relatively large amount of asset information over a relatively large distance. RFID tag-type reporting sources have no power source and are capable of communicating relatively small amounts of asset information, such as identifiers, over relatively short distances. In general, the better the capability of the reporting source, the more expensive it is. Therefore, it does not make good business sense to associate an expensive reporting source with a relatively cheap asset. According to one embodiment, this concern is addressed, among other things, by associating different types of reporting sources with different assets based on the characteristics of the asset and the goals of the construction project.

information about assets

According to one embodiment, asset-related information is received from a first reporting source and asset-related information is also received from a second reporting source. Information received from the two reporting sources may be stored in a database resulting in stored information. Refer to the description of step 406 (FIG. 4) for more information on expanding the database.

According to one embodiment, the information is asset location data. Examples of asset location data include, but are not limited to: whether the vehicle is on site, on the road, or in the correct area of the site. According to another embodiment, the information is asset operation data. Examples of asset operational data include, but are not limited to: the speed at which the asset is traveling, the elapsed time since the last oil change or other planned maintenance was performed on the asset, any indications of possible failure of the asset, and whether the vehicle is currently engaged, has previously been engaged, or will Participation in activities. Screeching sounds may be an indication of a possible asset failure.

Information can be used to determine: how much the asset has been used, where the asset is located, whether the asset is being used properly, whether the asset has left a designated area, such as bounded by a ground fence, when the asset needs maintenance, which service truck is best suited to perform the maintenance, etc. wait. Refer to the description of steps 402 and 404 of Part I (FIG. 4) for more information on "Information Related to Assets". Information about an asset can indicate what kind of event is happening to the asset.

Associate Reporting Sources with Assets

17 depicts a block diagram of associating different types of reporting sources with different assets based on the characteristics of the asset and the goals of the construction project, according to one embodiment. FIG. 17 depicts a bulldozer 1712 , large compressor 1718 , chop saw 1720 and bulldozer bucket 1716 . Assets are ranked according to their cost, their likelihood of moving around, and the amount of information that would typically be gathered about the asset. For example, bulldozer 1712 is more expensive, moves around more, and engages in more activities that may involve information gathering than compressor 1718 . More specifically, bulldozer 1712 will typically be constantly moving on a construction site, whereas compressor 1718 will tend to be relatively stationary. Bulldozer bucket 1716 provides no power and is subject to a fair amount of jostling.

1722、TrimTrac^TM 1724、MRS 1800和RFID标签1728与资产相关。图17描绘根据一个实施方案的与不同资产相关的若干个报告源。通常，推土机1712不断移动并且用于相对复杂的活动。因此，可能存在关于推土机1712的相对大量的信息。此外，资产管理系统可能需要密切留意推土机1712。因此，具有恒定电力供应并且能够频繁地将关于推土机的信息传输给资产管理系统的报告源(如1722)可与推土机1712相关。Cost, mobility, and amount of information about an asset are some examples of characteristics about an asset. How an asset will be used as part of a construction project and the amount of information an asset management system will collect to manage the asset are examples of construction project goals. Therefore, according to one embodiment, different types of reporting sources

1722, TrimTrac ^™ 1724, MRS 1800 and RFID tags 1728 are associated with the asset. Figure 17 depicts several reporting sources related to different assets, according to one embodiment. Typically, bulldozers 1712 are constantly on the move and are used for relatively complex activities. Accordingly, there may be a relatively large amount of information about bulldozer 1712 . Also, the asset management system may need to keep an eye on the bulldozer 1712. Therefore, reporting sources that have a constant power supply and are able to frequently transmit information about the bulldozer to the asset management system (such as 1722) can be associated with bulldozer 1712.

Large compressor 1718 rarely moves around. Therefore, a device capable of throttling power, such as the TrimTrac ^™ 1724, may be used. TrimTrac ^™ 1724 can detect when an asset 1718 associated with it is moved. When assets are stationary, the TrimTrac ^™ 1724 enters idle mode and conserves power. When it is detected that an asset is being moved, the TrimTrac ^™ 1724 enters an operational mode and starts transmitting information about the asset, which requires more power.

According to one embodiment, the installable reporting source (MRS) 1800 does not require power from the asset with which it is associated. According to one embodiment, installable reporting source 1800 is capable of communicating information about an asset, such as cutting saw 1720, to an asset management system. The RFID tag reporting source 1728 does not require power and is durable, and thus would be suitable for an asset such as a bulldozer bucket 1716 that is out of power and subject to a fair amount of vibration.

比RFID标签型报告源相对更昂贵。TrimTrac^TM和MRS 1800的成本介于两者之间。The more expensive the asset, the more reason to associate a relatively expensive reporting source with that asset. The more power and functionality a reporting source has, the more expensive the reporting source will be.

Relatively more expensive than RFID tag type reporting sources. TrimTrac ^TM and MRS 1800 cost somewhere in between.

TrimTrac^TM和MRS 1800能够将关于与其相关的资产的信息传递给资产管理系统，这是“主动”报告的实例。根据一个实施方案，RFID标签报告源被用作“被动”报告的一部分。例如，租赁公司或建筑公司通常具有一块场地，用来存放待赁或使用的资产(如压缩机)。雇员可以带着能够检测由与资产相关的RFID标签传输的识别符的数据收集器在场地周围走动。数据收集器可以是人能够拿在手中的装置。数据收集器可将来自资产的RFID标签的识别符传递给资产管理系统，以及传递其检测到资产识别符的存在的大致位置等。According to one embodiment,

The TrimTrac ^™ and MRS 1800 are capable of passing information about assets related to them to asset management systems, which is an example of "proactive" reporting. According to one embodiment, an RFID tag reporting source is used as part of the "passive" reporting. For example, a leasing company or construction company often has a site where assets (such as compressors) are stored for lease or use. Employees may walk around the site with data collectors capable of detecting identifiers transmitted by RFID tags associated with assets. A data collector may be a device that a person can hold in the hand. The data collector may communicate the identifier from the asset's RFID tag to the asset management system, as well as the approximate location where it detected the presence of the asset identifier, etc.

data collector

A data collector may be a device that a person can hold in the hand. As noted above, employees may walk around a site with data collectors capable of receiving identifiers transmitted by RFID tags associated with assets. The data collector can pass the identifier along with other information about the asset to the asset management system. Employees may enter information into the data collector, for example, to pass to the asset management system. Employees may display information about assets on the data collector in any manner that is beneficial to the employee. For example, the data collector can beep and display "Backhoe 123 has arrived."

和GIS型数据收集器是数据收集器的例子。Mobil Tech International^TM也制造数据收集器。根据一个实施方案，数据收集器可以是如由York在2003年8月29日申请并且标题为“Portable Electronic Instrumentwith Field-Replaceable Battery/Input/Output Module”、具有申请人档案号TRMB1412、转让给本发明的受让人的美国专利申请案第10/651,586号中所述的数据收集器。According to one embodiment, the data collector uses wireless technology.

and GIS type data collectors are examples of data collectors. Mobil Tech International ^(TM) also manufactures data collectors. According to one embodiment, the data collector may be as in the application by York on August 29, 2003 and titled "Portable Electronic Instrument with Field-Replaceable Battery/Input/Output Module", having applicant docket number TRMB1412, assigned to the present invention The data collector described in the assignee's U.S. Patent Application Serial No. 10/651,586.

Installable Reporting Sources

Figure 18 depicts a block diagram of an installable reporting source, according to one embodiment. The blocks representing features in FIG. 18 may be arranged differently than shown, and more or fewer features may be implemented than described herein. Furthermore, the features represented by the blocks in Fig. 18 may be combined in various ways. Installable reporting source 1800 may be implemented using software, hardware, firmware, or a combination thereof.

According to one embodiment, installable reporting source 1800 includes a controller 1810 , an interrogation component 1820 , a location determination component 1830 , and a consolidated asset information enabled communication component 1840 . An installable reporting source 1800 can be associated with an asset, for example, by installing the reporting source 1800 on the asset. The asset on which the installable reporting source 1800 is installed shall be referred to as a "related asset". According to one embodiment, installable reporting sources 1800 are associated with assets based on the characteristics of the asset and the goals of the construction project. For more information on associating an installable reporting source with an asset, see, inter alia, Part V, subheading "Associating Reporting Sources with Assets."

The controller 1810 is coupled to and controls the interrogation component 1820 , the location determination component 1830 and the consolidated asset information enabled communication component 1840 . According to one embodiment, the controller 1810 controls the receipt and execution of commands to determine a geographic location and communicate the location of an associated asset to, for example, an asset management system. According to another embodiment, the controller 1810 controls the transfer of information about related assets to the asset management system.

According to one embodiment, the query component 1820 can store the received identifier on the installable reporting source. According to another embodiment, the query component 1820 can access the stored identifier and can pass the identifier to the asset management system along with other pertinent information about the associated asset. According to one embodiment, the interrogation component 1820 stores the identifier in a radio frequency identification (RFID) tag, and receives the identifier from the RFID tag. The identifier can be passed, for example, to an asset management system along with other information about the asset.

According to one embodiment, the location determining component 1830 determines the location of the associated asset. According to one embodiment, the location determining component 1830 includes a Global Positioning System (GPS) antenna and a GPS receiver. However, various embodiments of the present invention are also well suited to utilize various terrestrial and satellite-based position determination systems.

According to one embodiment, merging asset information enables communication component 1840 to communicate information about the asset to, for example, an asset management system. According to one embodiment, inter alia, wireless communication is used to communicate information about the asset to the asset management system. Merge asset information enables communication component 1840 to communicate a portion of the information about the asset to the asset management system. For example, the installable reporting source 1800 can communicate the location of the asset and whether the asset requires maintenance to the asset management system.

The asset management system may also receive a second portion of information about the same asset from another reporting source. For example, an employee may use a handheld reporting source implemented with a personal digital assistant (PDA) to communicate that an asset is at risk. Thus, the asset management system enables the merging of two pieces of information about assets.

According to one embodiment, merging asset information enables communication component 1840 to communicate information about assets frequently. According to another embodiment, merging asset information enables communication component 1840 to communicate information about assets less frequently. For example, according to one embodiment, reporting source 1800 (FIG. 18) includes memory on which information about assets can be stored. Merge asset information enables communication component 1840 to periodically communicate the stored information to, for example, an asset management system.

Merge asset information enabling communication component 1800 can use a number of techniques to communicate, for example, with an asset management system. For example, the consolidated asset information enabled communication component 1800 can communicate using wireless fidelity (Wi-Fi), satellite, or internet protocol (IP) radio. See subheading "Communications" of Part V for more information.

According to one embodiment, the installable reporting source 1800 may use motion detectors that detect changes in motion of related assets to conserve power. For example, the installable reporting source 1800 may be in an idle mode when it is stationary, saving power. The motion detector can detect that the mountable reporting source 1800 is being moved by detecting vibrations and communicate this movement to the controller. When motion is detected, installable reporting source 1800 may switch to an operating mode that uses more power. Motion detectors can be accelerometers, tilt sensors, rotation sensors, gyroscopes, etc. Various devices for detecting movement are suitable for use as motion detectors.

Installable reporting sources 1800 may be added to an asset, for example, after the asset has been manufactured, purchased, and/or leased. According to one embodiment, the installable reporting source 1800 can be added to assets made by various manufacturers. Thus, the installable reporting source 1800 can be used as part of providing a common view of a construction project, regardless of the manufacturer of the asset. According to another embodiment, the installable reporting source 1800 is battery powered.

According to yet another embodiment, a Hewlett Packard ^™ (HP ^™ ) “Memory Spot” may be used as part of implementing the installable reporting source 1800 . HP ^(TM) Storage Points are small wireless data chips that can store between 256 kilobytes and 4 megabytes of information on flash memory. HP ^™ 's storage points provide RFID tags and also provide data rates orders of magnitude higher than conventional RFID tags. Storage points can store up to 250 times the data of RFID and can transmit data more than 20 times faster. Storage points can also encrypt data.

asset management system

Figure 19 depicts an asset management system for receiving information about a construction project, according to one embodiment. The blocks representing features in FIG. 19 may be configured differently than illustrated, and may implement additional or fewer features than those described herein. Furthermore, the features represented by the blocks in Fig. 19 may be combined in various ways. System 1900 may be implemented using software, hardware, firmware, or a combination thereof.

FIG. 19 depicts an asset management system 1900 that includes an asset information receiver 1910 and a database 1920 . Asset management system 1900 can include an asset information report generator 1930 that can generate optional reports 1940 . Asset management system 1900 may receive information about assets from more than one reporting source 1902 and 1904 . For example, a first reporting source 1902 may report a first portion of information about an asset, and a second reporting source 1904 may report a second portion of information about an asset. One of reporting sources 1902 and 1904 may be installable reporting source 1800 (FIG. 18). The asset management system 1900 can merge the two pieces of information about the asset and populate the database 1920 with the information about the asset. Similarly, asset management system 1900 may receive portions of information about other assets and populate database 1920 . Asset information generator 1930 can access information about assets stored on database 1920 and generate reports 1940 .

communication

According to one embodiment, Short Message Service (SMS), for example, is used for communication between devices and/or systems (such as reporting sources), data collectors and asset management systems. According to one embodiment, the unused portion of the communication channel is used to transfer small data packets of information between devices and/or systems. According to one embodiment, various channels of various technologies (such as digital, analog, 800 MHz, 1900 MHz, radio packet technologies) are scanned and the channel providing the best or at least acceptable level of service is selected. Examples of packet radio technologies include, but are not limited to, GPRS on GSM and 1XRTT on CDMA. Robustness and overall coverage are provided because there are many channels to choose from.

According to another embodiment, small packets of information are transmitted to a central hub on an existing Signaling System 7 (SS#7) network. Remote Access Application Messaging ^(TM) (RAAM ^(TM )) may be used as part of a small data packet for signaling on a selected channel. The hub can identify the service provider that is the intended recipient of the packet information and deliver the packet of information to the service provider, eg, on a backend link. Backend links can include Internet, dial-up, and dedicated connections.

Operational Examples of a Method for Receiving Information About a Construction Project

construction project

20 is a flowchart of a method for receiving information about a construction project, according to one embodiment. Although specific steps are disclosed in flowchart 2000, these steps are exemplary. That is, embodiments of the present invention are well suited for performing various other steps or variations of the steps set forth in flowchart 2000 . It should be appreciated that the steps in flowchart 2000 may be performed in a different order than presented and that not all steps in flowchart 1600 may be performed.

All or a portion of the implementation described in flowchart 2000 may be implemented using computer readable and computer executable instructions, for example, residing in a computer usable medium of a computer system or similar device. As noted above, in one embodiment, certain processes and steps of the present invention are implemented as a series of instructions (eg, a software program) residing in a computer-readable memory of a computer system and executed by the computer system. When executed, the instructions cause the computer system to perform the functions of the invention, as described below.

In step 2010, the method starts.

1722。相比之下，推土机铲斗1716较不昂贵，不提供电力并且更多地静止不动，因此RFID标签1728将适合它。In step 2020, different types of reporting sources are associated with different assets based on the characteristics of the asset and the goals of the construction project. For example, referring to the discussion of FIG. 17 under the subheading "Relating Reporting Sources to Assets," different reporting sources 1722-1728 are related to different assets 1712-1720 based on asset characteristics and goals of the construction project. More specifically, 1722 is related to bulldozer 1712. Bulldozer 1712 is a very expensive asset that generates a lot of information. In addition, a construction objective may be to keep an eye on bulldozers 1712 . Therefore, a relatively expensive reporting source is justified, such as one that has a continuous supply of power and is able to communicate frequently

1722. In contrast, bulldozer bucket 1716 is less expensive, does not provide power and is more stationary, so RFID tag 1728 would be suitable for it.

1722)能够在长距离上以相对频繁的基础提供关于资产的相对大量信息。其它报告源(诸如RFID标签1728)能够在短距离上仅提供关于资产的少量信息。根据一个实施方案，所使用的资产信息接收器对应于报告源的能力。例如，数据收集器对应于RFID标签型报告源1728的能力，因为人可将其带到相对靠近RFID标签型报告源1728的附近。相比之下，资产信息接收器1910(图19)对应于

1722、TrimTrac^TM 1724和MRS 1800的能力。In step 2030, an asset information receiver is used to receive information about an asset from a reporting source. An example of an asset information receiver is the data collector and asset information receiver 1910 (FIG. 19). According to one embodiment, the data collector forwards the information it has received to the asset information receiver 1910 . Some reporting sources (such as

1722) can provide relatively large amounts of information about assets on a relatively frequent basis over long distances. Other reporting sources, such as RFID tags 1728, can provide only small amounts of information about assets over short distances. According to one embodiment, the asset information receiver used corresponds to the capability of the reporting source. For example, a data collector corresponds to the capability of an RFID tag-type reporting source 1728 in that a person can bring it into relatively close proximity to an RFID-tag-type reporting source 1728 . In contrast, Asset Information Receiver 1910 (FIG. 19) corresponds to

1722, TrimTrac ^™ 1724 and MRS 1800 capabilities.

Two or more reporting sources are supported to provide information about a specific asset. For example, the consolidated asset information enabled communication component 1840 can communicate a portion of the information about the asset to the asset management system 1900 . For example, installable reporting source 1800 may communicate to asset management system 1900 the location of the asset and whether the asset requires maintenance. Asset management system 1900 may also receive a second portion of information about the same asset from another reporting source. For example, an employee may use a handheld data collector to communicate that an asset is at risk. Thus, the asset management system 1900 enables the merging of two pieces of information about an asset.

In step 2040, the method ends.

Part VI: Restricted Access to Asset Management Information

overview

According to one embodiment, information about assets may be selectively provided to various entities, such as leasing companies and construction companies. According to one embodiment, the information is stored in a database and includes information about assets owned by the leasing company and about assets leased to various construction companies. According to one embodiment, information about assets is selectively provided to various entities based on security concerns. For example, construction company C1 may only have access to information on assets it has leased, and construction company C2 may only have access to information on assets it has leased. According to one embodiment, a dealer may have access to information on any or all assets it owns. According to yet another embodiment, access to asset management information is restricted based on user preferences, as will become more apparent. While many embodiments are described with respect to dealerships, the various embodiments described herein will also work for rental companies that are not dealerships.

business model

21 is a block diagram depicting the relationship between a construction asset manufacturer, a leasing company 2120 that leases construction assets, and a construction company 2130, according to one embodiment. In the past, construction companies 2130 typically bought all of their construction assets. However, because of narrowing profit margins, construction companies 2130 prefer to buy a core set of assets and then lease additional assets when they do not have enough assets to do large construction projects. The construction company 2130 may lease these additional assets from the dealer 2122 or from a non-dealer leasing company 2124. Dealers 2122 are typically intermediaries between a particular manufacturer 2110 of construction assets, such as John Deere ^™ and Caterpillar ^™ , and construction companies 2130 . Examples of rental companies 2124 that are not dealers are United ^™ , Hertz ^™ and Volvo ^™ . Examples of architectural firms 2130 include, but are not limited to, Kuwaiti ^™ , Turner & Jacobs ^™ , and Rudolph and Sletten ^™ .

Because the construction company 2130 is more inclined to lease a certain portion of the asset it needs, the dealer sells less construction equipment. Therefore, the dealer 2122 enters the leasing business to make up the profit it no longer makes from the sale.

Figure 22 depicts various assets that two construction companies have leased from a dealer and a service truck owned by a dealer, according to one embodiment. The assets depicted in Figure 22 are three graders G1, G2 and G3, a bulldozer BD, two geofences GF1 and GF2, and two service trucks ST1 and ST2. For illustration, assume that construction companies C1 and C2 are two construction companies 2130 . To illustrate, assume that one construction company C1 has leased a bulldozer BD and a geofence GF1, and a second construction company C2 has leased three graders G1, G2, and G3 and a geofence GF2.

According to one embodiment, information about the assets depicted in Figure 22 is stored in a database. According to one embodiment, access to asset management information is restricted based on security concerns. For example, construction companies C1 and C2 wish to have information about their own assets available. However, a construction company 2130 may not want another construction company 2130 to have access to its information. Thus, according to one embodiment, company C1 only sees its own assets BD and GF1. A similar construction company C2 only sees its own assets G1, G2, G3 and GF2.

In addition, dealers 2122 also wish to obtain information about assets they own, lease out, and/or maintain. For example, dealer 2122 wishes to obtain information on ST1, ST2, BD, GF1, G1, G2, G3 and GF2. More specifically, it would be beneficial if the dealer 2122 could determine when and how much an asset has been used. For example, dealer 2122 may use various embodiments to determine whether construction company 2130 has used more assets than it paid for. In another example, as will become more apparent, the dealership 2122 may use various implementations to determine whether any assets require maintenance.

Using the various embodiments described herein, the dealer 2122 can have many different ways to increase its profits. In one example, reseller 2122 may sell reporting source 208 ( FIG. 2A ) to construction company 2130 . Construction company 2130 may use reporting source 208 to collect information that is transmitted to an asset management system owned by dealership 2122 . A construction company 2130 may use an asset management system to access information about assets it owns or leases. The dealership 2122 may charge the construction company 2130 for use of the asset management system, for example, on a monthly basis. The dealership 2122 may also charge the construction company 2130 a service fee when the dealership 2122 performs maintenance on assets leased or owned by the construction company 2130 .

asset management system

Figure 23 depicts a block diagram of an asset management system 2300 according to one embodiment. The blocks representing features in FIG. 23 may be configured differently than illustrated, and may implement additional or fewer features than those described herein. Furthermore, the features represented by the blocks in Fig. 23 may be combined in various ways. System 2300 may be implemented using software, hardware, firmware, or a combination thereof.

Asset management system 2300 includes an information store 2310 and an optional information access provider 2320 . The optional information access provider 2320 includes a permissions module 2322 . Information store 2310 may store information about assets in database 2330 , resulting in stored information 2340 . As will become more apparent, selective information access provider 2320 uses rights module 2322 to enable a first entity to access a first subset 2342 of information 2340 stored in database 2330 while not allowing a second entity to access information 2340 The first subset 2342. According to one embodiment, database 2330 is a relational database. According to one embodiment, database 205 ( FIG. 2A ) is an example of database 2330 depicted in FIG. 23 . According to one embodiment, SQL is used as part of retrieving information 2340 from database 2330 .

assets

Examples of assets include, but are not limited to, grinders, levelers, bulldozers, saws, debris vehicles, excavators, pavers, concrete trucks, supply trucks, cranes, tools, service trucks, geofences, compressors, and more. While many of the descriptions of the embodiments provided herein refer to building assets, the various embodiments are well suited to other types of assets as well.

According to one embodiment, the asset is owned by the leasing company 2120. The leasing company 2120 may lease the asset to the construction company 2130 . According to another embodiment, the property is owned by the construction company 2130. Various embodiments may be used by leasing company 2120 to maintain assets leased or owned by construction company 2130 . See Section I for more information on assets.

report source

2A, examples of reporting sources 208 include, but are not limited to, permanently installed devices 210, asset mountable/detachable devices 215, portable computing devices 220, personal digital assistants (PDAs) 225, smart phones 230, mobile phones 235, and manual Smart 240. See the discussion of reporting sources 208 in Section I for more information on reporting sources.

information

According to one embodiment, information about the asset is received from a first reporting source, and information about the asset is also received from a second reporting source. Information received from both sources may be stored in database 2330 , resulting in stored information 2340 . See the description of step 406 (FIG. 4) for more information on populating the database.

According to one embodiment, information 2340 is asset location data. Examples of asset location data include, but are not limited to, whether a vehicle is on a field, on a road, or in the correct field area. According to another embodiment, the information 2340 is asset operation data. Examples of asset operating data include, but are not limited to, the speed at which the asset is traveling, the time since the last oil change or other planned maintenance performed on the asset, any indications of possible failure of the asset, and the activity the vehicle is currently engaged in or has previously engaged in. Howling can be a sign of possible asset failure.

Information 2340 can be used to determine how much the asset has been used, where the asset is located, whether it is being used properly, whether it is leaving a designated area such as demarcated by a geo-fence, when the asset needs maintenance, which service truck is used to perform Maintenance is optimal, etc. See the description of steps 402 and 404 of Part I (FIG. 4) for more information on "information about assets".

Permissions and Security Questions

Figure 24 is a diagram illustrating the use of permissions to restrict access to asset management information according to one embodiment. FIG. 24 depicts a control domain 2410 , a data domain 2430 and a dependency 2420 between the control domain 2410 and the data domain 2430 . According to one embodiment, database 2330 includes control field 2410 , data field 2430 and dependencies 2420 . According to one embodiment, data field 2430 includes information about assets such as ST1, ST2, GF1, BD, GF2, G1, G2, and G3. Control domain 2410 may include passwords associated with entities such as dealer 2122 or construction companies C1, C2. According to one embodiment, the dealer's codes are associated with all assets ST1, ST2, GF1, BD, GF2, G1, G2 and G3, while the construction company 2130's respective codes are associated with the assets it leases. The solid lines indicate the correlation between the respective construction companies C1 and C2 and the respective assets they are leasing. Dashed lines indicate dependencies between dealer 2122 and assets owned by dealer 2122.

As depicted in Figure 24, all assets are owned by the dealer 2122. However, according to another embodiment, the asset may be owned by the construction company 2130. To illustrate, assume that construction company C1 owns graders G4 and G5. In this case, data field 2430 may include information about graders G4 and G5. Correlation 2420 may indicate that construction company C1's password may be used to access information about graders G4 and G5. However, construction company C2's password would not enable construction company C2 to access information about graders G4 and G5. According to another embodiment, correlation 2420 may also indicate that the dealer's password may be used to access information about graders G4 and G5, thus enabling dealer 2122 to provide maintenance on graders G4 and G5 owned by construction company C1 .

user preference

According to yet another embodiment, access to asset management information is restricted based on user preferences. For example, a project manager working for a construction company 2130 may be responsible for several projects. According to one embodiment, project managers have access to information about any or all projects for which they are responsible. Similarly, a regional office, local office, or national corporation may have access to information about any or all assets related to it, eg, based on user preferences.

Other examples of user preferences include asking to see how many assets of a particular type are located in a particular store. For example, a customer, such as an employee of a construction company 2130, may come in and inquire about a backhoe. Using various embodiments, an employee of the rental company 2120 may ask to see how many backhoes are available for rental from the outlet at that location. Furthermore, various implementations are provided for determining not only whether an asset is usable, but whether it is in good enough condition to be leased. For example, assume Customer 2130 wants to lease a bulldozer. According to one embodiment, employees of the rental company 2120 may use the asset management system 2300 to find available bulldozers at the rental store 2120 location. Assume 3 bulldozers are available. However, two bulldozers are due for maintenance. According to one embodiment, because the asset management system 2300 has access to information about maintenance, the asset management system 2300 can enable employees of the rental store 2120 to decide to lease a bulldozer that does not require maintenance.

In another example, a user may specify that they want to view information about an asset that will require maintenance within a certain period of time. Assets may be owned by a dealer 2122 or a construction company 2130. The asset may be maintained at the location of the leasing company 2120 or on a construction site. Additionally, dealer 2122 may use information 2340 stored in database 2330 to determine which service truck ST1 or ST2 is closest to the asset requiring maintenance.

According to one embodiment, the construction companies C1, C2 pay the dealer 2122 to maintain the property. The dealer 2122 may maintain assets leased from the dealer 2122 or owned by construction companies C1, C2.

Project managers, rental company employees, local administrators, area administrators, rental company owners, construction company employees are examples of possible users of the asset management system 2300, among others. According to various embodiments, users of the property management system 2300 may change the user preferences they are using, and the properties they access will change accordingly. For example, a project manager may request access to project A and then request access to project C. Selective information access provider 2320 may provide information about appropriate assets based on any user preferences required. According to one embodiment, SQL is used to retrieve information 2340 from database 2330 based on user preferences.

information dynamics

Information 2340 stored in database 2330 may change even as it is being viewed by various users. According to one embodiment, asset management system 2300 handles these types of dynamic changes to information 2340 . For example, two rental store employees A and B may be checking at the same time which backhoes are available. Assume that employee A rents out the backhoe while employee B is still viewing a display of which backhoes are available.

According to one embodiment, asset management system 2300 may prevent the same backhoe from being leased to two customers. For example, the asset management system 2300 may update the information displayed to Employee B as soon as the backhoe is leased. In another example, the asset management system 2300 does not immediately update the displayed backhoe that employee B sees. In this case, employee B may try to lease out the same backhoe. The asset management system 2300 may then inform Employee B that the backhoe has been leased.

Operational Example of Method for Restricting Access to Asset Management Information

Figure 25 is a flowchart of a method for restricting access to asset management information, according to one embodiment. Although certain steps are disclosed in flowchart 2500, these steps are exemplary. That is, embodiments of the present invention are well suited to perform various other steps or variations of the steps set forth in flowchart 2500 . It should be appreciated that the steps in flowchart 2500 may be performed in an order different from that presented, and that not all steps in flowchart 2500 may be performed.

All or a portion of the implementation described in flowchart 2500 may be implemented using computer-readable and computer-executable instructions, for example, residing in a computer-usable medium of a computer system or similar device. As noted above, in one embodiment, certain processes and steps of the present invention are implemented as a series of instructions (eg, a software program) residing in a computer-readable memory of a computer system and executed by the computer system. When executed, the instructions cause the computer system to perform the functions of the invention, as described below.

In step 2510, the method begins.

In step 2520, information about the asset is received from a first reporting source. For example, information for an asset may be received from a first reporting source 208, as depicted in FIGS. 22 and 24 . For illustration, assume that the first reporting source is asset installable/detachable device 215 . Device 215 may be installed on assets ST1, ST2, BD, G1-G3, and so on.

A reporting source, such as the asset mountable/detachable device 215 used in step 2520, can automatically detect when an asset has been returned to the dealer and cause the asset management system to automatically update the database 2330 indicating that the asset has been returned. Additionally, the reporting source may communicate any of the kinds of information that have been described herein to the database 2330 .

Other types of information about assets may also be received. See the discussion of step 402 for more information on receiving information about assets from a first reporting source. See the "Assets" subheading of Part VI for more information on the types of assets that can receive information. See the "Messages" subheading of Part VI for more information on the types of messages that can be received.

In step 2530, information about the asset is received from a second reporting source. For example, information for an asset may be received from a second reporting source 208, as depicted in FIGS. 22 and 24 . For illustration, assume that the second reporting source is a personal digital assistant 225 (PDA). An employee or dealer 2122 of the construction company C1, C2 can walk around and key in information about the assets ST1, ST2, BD, G1-G3 into the PDA 225. Thus, according to one embodiment, information about the asset may be received from more than one reporting source 208, as already described in Section I.

As described above, the device 215 can be used to automatically determine that the asset has been returned to the leasing company and cause the asset management system 2300 to update the database 2330 . Similarly, the second reporting source used in step 2530, such as the PDA 225, can be used to cause the asset management system 2300 to update the database 2330 when the asset is returned. Other types of information about assets may also be received. See the subheading "Information" of Section I and the discussion of step 404 for more information on "receiving information about assets from a second reporting source."

In step 2540, information from the first reporting source and the second reporting source is stored in a database. For example, information store 2310 may store information received in steps 2520 and 2530, resulting in stored information 2340 (FIG. 23). See the description of step 406 of Part I (FIG. 4) for more information on storing information in the database (also known as populating the database).

In step 2550, the first entity is enabled to access the first subset of information stored in the database, while the second entity is not allowed to access the first subset of information stored in the database. To illustrate, assume that the first entity is construction company C1 and the second entity is construction company C2, as discussed in the context of FIG. 22 . For illustration, assume further that information store 2310 stores information in database 2330 on assets (ST1, ST2, GF1, GF2, BD, G1, G2, and G3) owned by dealer 2122 and possibly leased. For illustration, further assume that subset 2342 of information 2340 is about assets BD and GF1 that construction company C1 is leasing. According to one embodiment, permissions module 2322 grants construction company C1 access to subset 2342 of information 2340 while disallowing construction company C2 to access subset 2342 of information 2340 .

Furthermore, according to another embodiment, the rights module 2322 grants the dealer 2122 access to the subset 2342 of the information 2340 while disallowing the construction company C2 to access the subset 2342 of the information 2340 . For purposes of illustration, assuming that the information 2340 stored in the database 2330 pertains to a particular dealership 2122, according to one embodiment, the subset 2122 includes all of the information 2340 stored in the database 2330 pertaining to the property.

According to one embodiment, when an entity wants to access information 2340, it may enter its password into a user interface (eg, in communication with asset management system 2300) (FIG. 23). The permissions module 2322 may use the password to determine whether the subset 2342 of the information 2340 is accessible. Selective information access provider 2320 may provide subset of information 2340 if rights module 2322 grants access to subset 2342 . See the "Permissions" subheading of Section VI for more information.

According to another embodiment, access to information about assets may also be restricted based on user preferences. For example, project managers, local administrators, nationwide corporations, etc. may use user preferences to limit access to information of genuine interest to them. For example, a project manager may be interested in viewing information about project C. It may then be interested in viewing information about item B.

In another example, a leasing company owner may be interested in how many assets of a particular type are available for immediate leasing.

In another example of user preference, a user may specify that they want to view information about assets that will require maintenance within a certain period of time. Assets can be owned by dealers 2122 or construction companies 2330. The asset may be maintained at the location of the leasing company 2120 or on a construction site. For more information about user preferences, see the subheading "User Preferences" in Section VI.

In step 2560, the method ends.

in conclusion

Various embodiments of the invention can be used to restrict access to asset management information. Access can be restricted based on security concerns or based on user preferences. By enabling customers, such as construction companies, to access the appropriate level of information, rental companies, whether dealers or not, can improve their relationship with their customers, which can lead to increased profits.

By enabling leasing companies to view the appropriate level of information, leasing companies are less likely to miss out on opportunities to lease assets. For example, conventional leasing companies use a manual process of updating their asset tracking systems, and therefore take a long time to key returned assets into the system. Therefore, a leasing company using conventional methods may think it has an asset stock when it does not, resulting in missed leasing opportunities. However, using various embodiments of the present invention, the asset management system is updated immediately when the asset is returned, so less opportunities will be missed by the leasing company. Additionally, various implementations enable leasing companies to determine how long an asset has been used. The leasing company can charge the construction company more if the asset is used longer than the construction company paid for it. Various embodiments also enable leasing companies to determine whether assets have been used properly, among other things.

While many embodiments are described with respect to dealerships, the various embodiments described herein will also work for rental companies that are not dealerships. While many of the embodiments described herein refer to dealerships, leasing companies, and construction companies, various embodiments may be used for other types of businesses involved in asset management. While many of the embodiments described herein refer to building assets, various embodiments that limit access to information about other types of assets may also be used.

Part VII: External Expansion Asset Management

overview

Embodiments described herein provide a method and system for externally extended asset management. In general, the embodiments described herein utilize multiple, distinct sources for monitoring an asset and its environment. The disparate sources provide asset operational and environmental information that populates the database. The database is organized to combine multiple asset and environmental information, resulting in a single source of organized asset information. The resulting database will provide a vast plethora of asset management data with a depth significantly greater than can be provided by a single piece of information.

In addition, by utilizing multiple disparate sources to provide asset and environmental information, the asset manager's asset awareness will be significantly increased while the chance of asset error is significantly reduced. In other words, a single asset or environmental source reporter error will not result in a complete loss of the asset manager's asset management capabilities.

Furthermore, due to the asset management capabilities described herein, an important business management tool is implemented. That is, because the asset management system is applicable to all levels of asset management, the asset management system provides significant value-added features at the manufacturer level, lease/lease level, and owner level. Furthermore, value-added features can be very similar to "sell-it-yourself" features.

Referring now to FIG. 26, a network diagram of an exemplary method for externally extended asset management is shown, according to one embodiment of the present invention. Asset management network 200 includes database 205 , plurality of reporting sources 208 , at least one environmental condition reporting source 2608 , and local business intelligence database 2653 .

In general, database 205 receives information from at least two reporting sources 208 and organizes data within database 205 such that information about assets can be corroborated. For example, data within database 205 can be organized such that information about a particular asset or assets can be ascertained. This capability has been described with reference to FIG. 2A and is not repeated here for the sake of brevity.

In one embodiment, database 205 is a single database on a single computing system (eg, computing system 100). In another embodiment, database 205 may actually consist of multiple databases on a single computing system or on multiple computing systems. Additionally, the multiple databases may be at the same location or spread across multiple locations. Additionally, the plurality of databases may be coupled together by wire or wirelessly to form a network of databases on which asset information may be stored. In one embodiment, the asset may be machinery, vehicles, electrical or mechanical equipment, inanimate objects, or any other trackable item.

Environmental reporting sources 2608 include devices such as, but not limited to, weather reporting stations 2610 , traffic reporting stations 2615 , and imagery providers 2620 . Additionally, reporting sources 2608 may include sources such as electronic devices, human sources, assets being monitored, other assets, and the like. The local business intelligence database 2653 may be a local data source about the environment, such as a local library or a database maintaining environmental data. In one embodiment, environmental data may include soil maps, geological maps, geographic maps, design files, imagery (e.g., satellite, video, still, etc.), historical features, environmental regulations, protected flora and fauna, points of interest wait. In one embodiment, any or all of the environmental condition reporting sources 2608 are capable of providing environmental condition information, including but not limited to traffic information, weather information, environmental information, video or still images, and the like.

In general, weather reporting stations 2610 may be Internet climate sources, weather satellites, weather band radios, weather stations, human reports about weather, etc. that provide local, general, or other weather related information. For example, the weather reporting station 2610 may provide daily/weekly temperature ranges, precipitation, rainstorm information, sky description (eg, cloudy, clear, foggy, etc.), forecasts, and the like. That is, weather reporting stations 2610 will provide supplemental environmental information to database 205 to provide actual weather for areas where the asset may be operated, areas where the asset should be operated, areas where the asset has previously been operated, or any combination thereof condition.

In general, reported weather information can be used for both short-term and long-term planning. For example, in the short term, if assets are required at multiple locations, weather information can be reviewed at each project location. For an asset, if the weather is not suitable at a first location, but is suitable at a second location, the asset may be assigned to the second location. In doing so, rather than sending the asset to a first project location (where weather conditions are incompatible resulting in limited or unavailable use of the asset), the asset will be in an operational environment. Over the longer term, weather history can be reviewed to infer expected working days, likely ground conditions, initial construction needs, etc. In one embodiment, long-term planning may provide a means of allocating assets, providing initial human resource planning, and the like.

Traffic reporting stations 2615 may be internet traffic sources, traffic cameras, traffic radios, traffic metering devices, human reports about traffic, or similar reporting stations that provide local, general, or other traffic-related information. For example, the traffic reporting station 2615 may provide daily/weekly updated traffic information, accident reports, delays, etc. That is, the traffic reporting station 2615 will provide supplemental environmental information to the database 205 to provide actual traffic for areas where the asset may be operated, areas where the asset should be operated, areas where the asset has previously been operated, or any combination thereof condition. For example, if an asset is moving to a location, traffic reports can be used to generate an optimal route, provide real-time rerouting based on current traffic conditions, etc. In addition, traffic information can provide a predicted route based on the time of day, traffic accidents, road construction, etc.

Imagery providers 2620 may be internet cameras, traffic cameras, satellites, images taken by people, or the like that provide imagery related to local, general, or other environmental conditions. For example, imagery provider 2620 may provide daily/weekly/monthly/yearly imagery for any selected environment (such as a job location), selected location, etc. That is, imagery provider 2620 will provide supplemental environmental information to provide actual imagery of areas where the asset may be operated, areas where the asset should be operated, areas where the asset has previously been operated, or any combination thereof.

In one embodiment, each reporting source 2608 may include capabilities such as position fixation, photography, text messaging, voice signaling, data signaling, radio frequency identification tag reading, and the like. Also, in one embodiment, any or all of reporting sources 2608 may be capable of monitoring environmental conditions at one or more locations. For example, any or all reporting sources 2608 may be capable of providing precise location information, general regional information, and the like.

Referring now to FIG. 27, an exemplary externally augmented asset management system 700 is shown communicatively coupled with an optional client application 710, in accordance with one embodiment of the present invention. Asset management system 700 is comprised of data receiver 330 , database 205 and optional asset information report generator 750 .

In general, data receiver 330 is configured to receive information about assets from multiple reporting sources (eg, sources 208A and 208B). Additionally, data receiver 330 is configured to receive information about the environment from at least one environment reporting source 2608 . The data receiver 330 reports this asset information to the database 205, and then uses the first portion of the information about the asset from the first reporting source 208A, the second portion of the information about the asset from the second reporting source 208B, and the information from the report about the asset. Database 205 is populated by other reporting sources of information on assets, and the like. Additionally, database 205 may similarly receive and maintain information regarding multiple assets. The specific functions and operations of data receivers 330 and database 205 with respect to asset information reporting sources (e.g., 208A and 208B) have been previously described, and for the sake of brevity, the description will not be repeated here unless it is necessary to identify any differences or previous Features not described.

At least one environmental reporting source 2608 provides environmental condition information to database 205 in any or all of a number of ways. In general, the environmental information received by database 205 may be directed to the location of the asset, to the region in which the asset is operated, or to the region in which it is planned to operate the asset. For example, if the asset is moving on a highway, the environmental information received by the database 205 may include traffic information, accident information, weather information, imagery from the highway, and the like. Additionally, in one embodiment, the contextual information received by the database 205 may be time-stamped and include location information, or otherwise symbolized, to ensure that both time and location are verifiable. However, in another embodiment, the environmental information received by the database 205 may only be time stamped or include location information. In yet another embodiment, the contextual information received by the database 205 may not be time stamped and may not include location information or other symbols.

The specific functions and operations of optional asset information report generator 750, optional report 360, and optional client application 710 have been previously described herein and will not be repeated for purposes of brevity.

Figure 28 is a flowchart 2800 of an exemplary method for providing externally extended asset management, according to one embodiment of the present invention. In FIG. 28, elements 402 and 404 have been previously described, and for the sake of brevity, the description will not be repeated. Instead, reference is made to the previous description of these flowchart elements.

Referring now to 2806 of FIG. 28 and FIG. 27 , one embodiment receives environmental condition information about an asset from a third reporting source 2608 . As described in detail herein, in one embodiment, the environmental condition information is received by database 205 via data receiver 330 . The information can be received by wire or wirelessly and through a direct connection of the reporting source and data sink 330 or over a network.

In one embodiment, data receiver 330 receives environmental condition data from third reporting source 2608 . As described herein, environmental condition data refers to environmental conditions related to geographic locations. For example, if the asset is a vehicle, the environmental condition data may include, but not limited to, the weather (for example, sunny, foggy, rainy, etc.), road conditions (for example, delays, accidents, road closures, etc.) . Generally, environmental condition data is received from sources such as, but not limited to, weather stations, the Internet, radio stations, traffic cameras, satellites, human intelligence (HumInt), and the like.

Furthermore, while only one environmental condition reporting source 2608 is shown, the present invention is well suited for receiving environmental condition information from multiple environmental condition reporting sources 2608 (as shown in FIG. 26 ), as described herein. For example, in one embodiment, data receiver 330 may receive environmental condition information from multiple sources, such as any or all of sources 2610-2615.

Referring now to 2808 of FIG. 28 and FIG. 27, one embodiment populates the database 205 with information from the first reporting source 208A, the second reporting source 208B, and the third reporting source 2608 so that information about the asset and its operating environment is available from the database. 205 confirmed. In one embodiment, database 205 provides real-time location and/or operational monitoring capabilities of assets and their environment. In another embodiment, database 205 provides near real-time location and/or operational monitoring capabilities of assets and their environment.

That is, any or all of the reporting sources 208 that provide information about assets and the environmental condition reporting sources 2608 that provide environmental information may be configured to provide information frequently, periodically to provide scheduled information updates, or to provide information updates only when requested by the user .

For example, the environmental condition reporting source may be a traffic reporting device 2615, such as a highway traffic camera or the like. The traffic reporting device 2615 may provide frequent highway information updates to the database. This can be important if the asset is regularly utilizing the highway. For example, the asset may be ready to move from point A to point B. However, by accessing the database, users will be able to ascertain whether regular routes are available, alternate routes are desirable, or other traffic conditions that can provide insight to improve asset utilization efficiency.

In another example, the traffic reporting device 2615 may be used by the rental company to ensure the validity of the lessee's excuse. For example, if a lessee calls on a Friday night and tells the leasing company that the asset cannot be returned before closing due to traffic delays, the leasing company will be able to check against the database, e.g. The aforementioned assets are indeed in a traffic jam. Thus, not only would the rental company be able to monitor the property after a "traffic jam" call to see if it was being used on the weekend, but the rental company would also be able to check to see if the property was actually blocked.

In the same way, any information about the environment may be updated frequently, the use of traffic information here is provided as an example for simplicity purposes only. However, if the environmental conditions do not need to be updated frequently, then the information may not be provided to the database 205 as often. Using traffic again as an example, environmental condition traffic information may only be provided at scheduled update times if the asset is located in the same region, eg, it will be needed in the same location one day, it is damaged, unused, awaiting maintenance, etc. For example, environmental conditions can be checked in the morning and again in the evening, or only once a day, or only once a week, etc. Additionally, environmental condition information may be modified based on asset status. That is, environmental condition information may only be updated periodically or not if the asset is inactive. However, as the asset becomes operational, the environmental condition information may be updated on a more regular basis, or even frequently.

Additionally, in one embodiment, environmental conditions and asset information are presented in the form of an asset information report 750 generated from data in the database 205 . In one embodiment, the data presented in the Environmental Conditions and Asset Information Report 750 is a combination of all received information about the asset and its environment. However, in another embodiment, the data presented in the asset information report 750 is a combination of the information section received only about the asset and/or the environmental condition information section.

For example, database 205 may have redundant information about assets and environmental conditions from multiple reporting sources. That is, multiple reporting sources may provide environmental conditions and asset location information. In one embodiment, when generating the asset information report 360, all information in the database about the asset and environmental conditions, including redundant information, may be used by the report generator 750. However, in another embodiment, report generator 750 may remove redundant information prior to generating asset information report 360 to reduce bandwidth, increase report clarity, and the like. In yet another embodiment, redundant information may be removed at the database level to manage the size of the database 205 .

Additionally, in one embodiment, asset information report 360 may be presented on a GUI, reproduced on paper, may be provided in audio, or may be provided in another user-selected format. For example, asset information reports may be provided to users in formats other than visual formats at times such as when asset information reports are provided over a communications network, or to visually impaired Users reviewing visual asset information reports, etc.

Accordingly, embodiments of the present invention provide an externally extended asset management system and method. Embodiments further provide automated methods to customize asset information reporting both visually and electronically. Embodiments also provide automated methods for receiving information reports from external applications that run independently of the extension management system. Additionally, methods and systems are provided for combining external information and asset management information in one electronic file formatted for a client application or for manually or automatically providing the formatted file to a client application.

Part VIII: Temporary Asset Tracking

Temporary Asset Tracking System

An ad hoc asset tracking system utilizes an asset management system, such as asset management system 700, and utilizes the reporting capabilities of one or more reporting sources, such as reporting sources 208A and 208B (FIG. 3), to collect information encountered on an ad hoc basis. Secondary reporting of identifying information associated with assets received, such as when driving past rental equipment in a rental facility or passing construction equipment assets in a construction yard. One example of using reporting sources such as 208A and 208B to send such secondary reports is described in conjunction with FIG. 30 and illustrated by FIG. 31 .

Referring now to FIG. 29, a block diagram of an exemplary asset management system 700 utilized as a temporary asset tracking system is shown, according to one embodiment of the present invention. Asset management system 700 is comprised of data receiver 330 , database 205 , optional asset information report generator 750 and optional discovered asset notification module 2980 . The specific functions and operations of data receiver 330, database 205, and asset information report generator 750 have been described previously and will not be repeated here for the sake of brevity unless necessary to identify any different or previously not described features.

In general, data receiver 330 is configured to receive information about assets from multiple reporting sources (eg, sources 208A and 208B). As seen below, in one embodiment, this also includes receiving asset identification data and asset identification information collected, for example, on an ad hoc basis and then reported by reporting sources such as reporting sources 208A and 208B. In one embodiment, data receiver 330 reports such asset identification data and asset identification information to a database, such as database 205, which is then populated with the asset identification data and asset identification information. In certain embodiments, such asset identification information and asset identification data are stored in the same database 205 as previously described asset information that has been received from the first reporting source 208A, the second reporting source 208B, and/or other reporting sources. middle. In one embodiment, optional asset information report generator 750 is used to assign asset groups and locations, assign report source groups, and generate asset information from the asset information, asset identification data, and asset identification information held in database 205. Information Report 360. As will be seen, in one embodiment, this includes generating an asset information report 360 that includes asset identification information gathered for the asset on an ad hoc basis.

In one embodiment, an optional found asset notification module 2980 is connected to the asset information report generator and database 205 and is used to register or "flag" assets of interest. An optional found asset notification module 2980 provides a user interface that allows tagging information, such as serial number, asset type, or inventory quantity of an asset. A tagged asset can be a lost or misplaced asset, or simply an asset whose location the user has a particular interest in finding. Upon entering such asset tagging information, the asset discovery notification module 2980 monitors the database 205 for any identifying information or identifying data related to the tagged asset, which is then populated into the database 205 .

In one embodiment, the user accesses any subsequently populated location information about the tagged asset at a later time, such as through asset information reporting 360 or via a graphical user interface provided by asset information reporting module 750 . In one embodiment, the optional asset found notification module 2980 allows the user to choose to receive optional notifications 2960 from the asset found notification module 2980, such as, for example, a text message, text message, page number, cell phone call or email. Although shown separately for purposes of brevity, it should be understood that in one embodiment, the discovered asset notification module 2980 is integrated with another portion of the asset management system 700 , such as the asset information report generator 750 .

Method for Temporary Tracking of Assets

FIG. 30 is a flowchart of an exemplary method 3000 of temporarily tracking the location of an asset, according to an embodiment of the invention.

Referring now to element 3002 of FIG. 30 and FIG. 29, one embodiment receives information from a first reporting source 208A about a first asset. The first reporting source 208A is coupled to the first asset. This receipt of information is consistent with the receipt of information about assets described in connection with 402 of method 400, except that reporting source 208 is coupled to the asset to which the reporting information pertains. This is in contrast to reporting source 208 in element 402, which may or may not be coupled to the asset the information was reported on. As previously described, the information received from reporting source 208A may be location information or operational information about the asset. Figure 31 provides an example of two such reporting sources (208A and 208B) that interface with construction vehicles and report asset information about their respective vehicles.

Referring now to FIG. 31 , a diagram of an exemplary embodiment for temporarily tracking asset location is shown, in accordance with an embodiment of the present invention. In FIG. 31 , an area is shown by area 3100 , such as a rental equipment site, property sales lot, or construction site. For this example, it may be assumed that area 3100 represents a construction site. In a construction site 3100, short-range communication devices 3101, 3102, and 3103 are located. Figure 31 also shows a loader 3115 equipped with a first reporting source 208A and a dump truck 3120 equipped with a second reporting source 208B.

装置、移动电话(例如，蜂窝电话)、个人数字助理、便携式计算装置、射频识别符、智能电话等。The primary purpose of the reporting sources 208A and 208B is to report location information and/or operational information about the asset, and thus each have an information module coupled thereto for gathering information related to the asset. For example, the primary purpose of the reporting source 208A in this example is to report location information and/or operational information about the loader 3115 coupled thereto. Similarly, the primary purpose of reporting source 208B in this example is to report location and/or operational information about dump truck 3120 coupled thereto. As previously mentioned, reporting sources 208A and 208B may include (or be configured with) global navigation satellite system (GNSS) receivers to facilitate reporting of location information. Likewise, reporting sources 208A and 208B may be coupled to one or more operational information providing sources coupled to each, such as J-buses for respective assets, asset processors, diagnostic evaluators, engine microprocessors, mileage indicators gauge, speedometer, tachometer, oil pressure indicator, wheel pressure indicator, hydraulic pressure indicator, engine time and ignition switch power. As previously indicated, in various embodiments, a reporting source (such as 208A and/or 208B) may include a TrimTrac ^™ device,

devices, mobile phones (eg, cellular phones), personal digital assistants, portable computing devices, radio frequency identifiers, smartphones, and the like.

Referring now to 3004 of FIG. 30, an embodiment receives asset identification information about a second asset from a first reporting source. In one embodiment, the asset identification information includes information collected by a first reporting source on an ad-hoc basis while said first reporting source is within transmission range of a short-range communication device connected to said second asset. identification data. In certain embodiments, receiving asset identification information includes receiving asset identification data alone, or otherwise in combination with other information, such as location information and/or time information.

In one embodiment, for example, when the identifying data is collected, it is combined with the location of the reporting source 208A. For example, a geographic location (latitude and longitude) or a specific location or region in which the reporting source 208A operates. In one embodiment, these position data originate from a Global Navigation Satellite System (GNSS) receiver of reporting source 208A. In another embodiment, the identifying data is combined with the time when the reporting source 208A collected the identifying data. The time may be taken from an internal clock of reporting source 208A, or may come from an external source, such as a satellite signal or a cell phone signal received by reporting source 208A.

"Temporary basis" means that gathering and reporting information about additional assets is a secondary function of the first reporting source 208A that occurs only, e.g. The result is within transmission range of asset identification data generated by the distance communication device (3101, 3102, 3103). Although the collection of identifying data occurs on an ad-hoc basis, the occurrence of such collecting of identifying data may be deliberate or accidental. Thus, in instances where the reporting source 208A is connected to a vehicle, the vehicle may deliberately drive through an area to encounter additional assets in the area and gather identifying data about these additional assets. Likewise, even without such purposeful operator intent, reporting source 208A will still gather information from additional assets encountered as the vehicle drives around randomly, or in the performance of some other task.

Referring again to FIG. 31 , reporting sources 208A and 208B are each configured to collect secondary information gathered about additional assets, such as from identification data transmitted by short-range communication devices connected to those additional assets. To this end, each reporting source (208A, 208B) is configured with a short-range communication device, such as a radio frequency identification (RFID) reader, a Bluetooth device, and/or a wireless fidelity (WiFi) wireless local area network (WLAN) The additional assets of the communication device collect identification data. The collected identification data is then reported to a data receiver, such as data receiver 330, via a transmitter (eg, via a cell phone) (FIG. 29). Such reporting is performed in the same manner as previously described for primary reporting of asset operational information and/or asset location information reported by reporting sources 208A and 208B. For this example, it may be assumed that reporting sources 208A and 208B are each equipped with an RFID reader, a Bluetooth communicator, and a WiFi communicator.

The short-range communication devices 3101, 3102, and 3103 are communication devices having a limited transmission range such as several centimeters to tens of meters. The short-range communication devices (3101, 3102, and 3103) include devices such as, but not limited to, radio frequency identification (RFID) tags, wireless fidelity (WiFi) devices, or Bluetooth devices. For this example, it may be assumed that device 3101 is an RFID tag, device 3102 is a WiFi device, and device 3103 is a Bluetooth device. Although these short-range communication devices have limited transmission range, they have advantages such as low cost, low power requirements (and in some cases, no power requirements), small footprints, and robustness. The operation of these short-range communication devices is well known and, for the sake of brevity, will not be described in detail here.

装置)，对于主动资产管理使能装置太小，或没有针对主动资产管理使能装置的功率。对各近距离通信装置(3101、3102、3103)编程以传输和与其耦接的资产关联的识别数据。这种识别数据可包括：车辆识别号、序列号、资产类型(例如，发电机、便携式灯、装载机桶或某些其它资产类型)、型号、与所述资产关联的库存号、或关于与近距离通信装置(3101、3102、3103)连接的资产的某些其它描述信息。对于这个实例，可假定RFID标签3101是与装载机桶3171耦接且被构造成在有限范围3111内传输包括装载机桶资产3171的序列号的信号。同样地，在这个实例中，WiFi装置3102是与便携式灯3172耦接且被构造成在有限范围3112内传输包括与便携式灯资产3172关联的库存号的信号。最后，蓝牙装置3103是与发电机3173耦接且被构造成在有限范围3113内传输包括与发电机资产3173关联的序列号的信号。In FIG. 31, each NFC device (3101, 3102, 3103) is coupled to an asset, such as a building equipment asset whose value does not justify an "active" asset management enabling device (such as a TrimTrac ^™ device or

devices), are too small for active asset management enabled devices, or do not have the power for active asset management enabled devices. Each short-range communication device (3101, 3102, 3103) is programmed to transmit identification data associated with an asset to which it is coupled. Such identification data may include: vehicle identification number, serial number, type of asset (e.g., generator, portable light, loader bucket, or some other type of asset), model, inventory number associated with said asset, or Some other descriptive information of the asset to which the near field communication device (3101, 3102, 3103) is connected. For this example, it may be assumed that RFID tag 3101 is coupled to loader bucket 3171 and is configured to transmit a signal including the serial number of loader bucket asset 3171 within a limited range 3111 . Likewise, in this example, WiFi device 3102 is coupled to portable light 3172 and is configured to transmit within limited range 3112 a signal including an inventory number associated with portable light asset 3172 . Finally, a Bluetooth device 3103 is coupled to the generator 3173 and is configured to transmit within a limited range 3113 a signal including a serial number associated with the generator asset 3173 .

As loader 3115 travels on path 3116 through construction site 3100 , it enters transmission range 3113 and reporting source 208A gathers identification data from Bluetooth device 3103 . The reporting source 208A records the location of the loader 3115 when the identification data was collected and/or the time when the identification data was collected from the Bluetooth device 3103 . As loader 3115 continues to pass transmission range 3112 , reporting source 208A collects identifying data from WiFi device 3102 . The reporting source 208A records the location of the loader 3115 when the identification data was collected and/or the time when the identification data was collected from the WiFi device 3102 . At certain points in time, such as immediately after the identification data is collected, after being queried, or at a predetermined time, the reporting source 208A reports the collected identification information (identification data combined with collection location and/or collection time) to the data sink 330.

In a similar manner, as dump truck 3120 travels on path 3121 through construction site 3100 , it enters transmission range 3111 and reporting source 208B collects identification data from RFID tag 3101 . The reporting source 208B records the location of the dump truck 3120 when the identification data was collected and/or the time when the identification data was collected from the RFID device 3101. Similarly, reporting source 208B gathers identification data from Bluetooth device 3103 as dump truck 3120 enters transmission range 3113 . The reporting source 208B records the location of the dump truck 3120 when the identification data was collected and/or the time when the identification data was collected from the Bluetooth device 3103 . At certain points in time, such as immediately after the information is collected, after being queried, or at a predetermined time, the reporting source 208B reports collected identification information (identification data combined with collection location and/or collection time) to data receiver 330 .

Referring now to 3006 of FIG. 30 and FIGS. 29 and 31 , one embodiment populates the database 205 with asset identification information. The information is populated so that it can later be collected from the database 205, for example, for use in asset information reports. Thus, in the embodiment illustrated by FIG. 31 , the identification information received by data receiver 330 is populated into a database (such as database 205 ), which is associated with the assigned asset. In one embodiment, this includes populating identifying information received from other reporting sources, such as reporting source 208B. Accordingly, the identification information for a particular asset that is populated into the database 205 may be identification information received from a single reporting source or multiple reporting sources. It should be appreciated that, in one embodiment, such identifying information is populated in a different database than database 205 . It should also be appreciated that such identifying information may be populated into or separate from a database shared with other asset information received from reporting sources, such as reporting sources 208A and 208B.

Additionally, while method 3000 and FIG. 31 have been described in connection with an exemplary embodiment in which near-field communication devices 3101, 3102, and 3103 are coupled to construction equipment assets, it should be appreciated that in other embodiments, such near-field communication devices It can also be coupled to other assets, such as rental equipment assets, materials (e.g., I-beams, windows, furniture), or packaging materials (e.g., pallets, boxes) for use in reporting sources such as report The purpose of tracking such assets on an ad-hoc basis when within transmission range of the source 208A). Also, while only 3 near-field communication devices are shown in FIG. 31, it should be appreciated that in other examples tens, hundreds, or more may be utilized, each coupled to an asset and configured to communicate with all Identifying data associated with the asset.

Similarly, in one embodiment, a reporting source, such as reporting source 208A or 208B, is capable of collecting and reporting (transmitting) individual asset identification information gathered through temporal interactions with such multiple short-range communication devices. Thus, in one embodiment, the reporting source 208B receives a plurality of signals from a plurality of RFID tags coupled to a plurality of assets separate from, loaded in, or coupled to the dump truck 3120, And this is encountered during operation of the dump truck 3120. Reporting source 3120 then reports (such as transmitted by a cell phone) identifying information associated with the plurality of assets. The identification information is received by the data receiver 330 and then populated into the database 205 .

Additionally, while the reporting sources 208A and 208B have been described as being connected to a construction vehicle, it should be appreciated that in other embodiments such reporting sources may have other configurations. For example, in one embodiment, reporting source 208A includes a GNSS receiver and RFID reader coupled to a cellular phone. In this embodiment, reporting source 208A may be carried by the individual and will similarly report identifying information collected on an ad-hoc basis during the individual's travels and movements. In such an embodiment, the primary information reported by a reporting source (such as 208A) is the location of the asset carrying the reporting source (which in this case is an individual, such as a construction manager). The secondary information reported is asset identification information collected on an ad-hoc basis as reporting source 208A moves through leased premises, sales piles, construction yards, etc., including assets equipped with near-field communication sources such as RFID tags 3101 .

Reports and Notifications

In one embodiment, the asset identification information is presented in the form of an asset information report 360 generated from data in the database 205 . In one embodiment, the data presented in the asset information report 360 is a combination of all information received about the asset from the various reporting sources 208 . However, in another embodiment, the data presented in the asset information report 360 is only a combination of information received from any or all of the reporting sources 208 about the asset in part.

Asset identification information in a database such as database 205 may have redundant information about the asset from multiple reporting sources 208 . That is, multiple reporting sources 208 may provide asset location information. For example, as illustrated in FIG. 31 , reporting sources 208A and 208B each gather identification data from a short-range communication source 3103 coupled to a generator 3173 . Likewise, reporting sources 208A and 208B each report identifying information associated with generator 3173 . In one embodiment, all identifying information about an asset in database 205 (including redundant information) may be used by report generator 750 when generating asset information report 360 . However, in another embodiment, report generator 750 may remove redundant information prior to generating asset information report 360 to reduce bandwidth, increase clarity, and the like. In yet another embodiment, redundant information may be removed at the database level to manage the size of the database 205 . Asset information report generator 750 may combine asset information and asset identification information into a single asset information report 360 or generate separate asset information reports 360 with each type of information. Accordingly, in one embodiment, asset information report generator 750 generates asset information report 360 that includes at least a portion of asset identification information.

Additionally, in one embodiment, asset information report 360 may be presented on a GUI, reproduced on paper, may be provided in audio, or may be provided in another user-selected format. For example, asset information reports may be provided to users in formats other than visual formats at times such as when asset information reports are provided over a communications network, or to visually impaired Users reviewing visual asset information reports, etc.

Referring now to FIG. 32 , a block diagram of an exemplary printable format 3200 of an asset information report 360 generated by an asset management system 700 is shown, in accordance with one embodiment of the present invention. Exemplary printable format 3200 may also be viewed, such as on a video monitor connected to a computer, or on the screen of a personal digital assistant. As can be seen in FIG. 32 , the asset information report generator 750 has extracted from the database 205 the identifying information provided by the near field communication device 3103 coupled to the generator asset 3173 . In one embodiment, the asset information report generator 750 provides a title 3205, such as "Asset Location Report." Such an asset location report may provide location information for an asset, a category of assets, or a group of assets. For example, in one embodiment, asset information report 360 includes an asset location report for a group of assets that have been assigned by asset information report generator 750 to a particular geo-fenced area, such as a construction site.

Printable format 3200 displays identifying information from database 205 as an asset location report for an asset. The report 3200 is formatted in columns corresponding to the asset 3202, the time 3203 when the asset identifying data was collected by the reporting source, and the location 3204 of the reporting source when the identifying data was collected. Column 3202 shows that the asset is a generator. Column 3202 shows the various times (including dates), in this case, the generator's identifying information received by the reporting source. Column 3204 displays the various locations of the reporting source corresponding to the different times at which identifying data was collected by the reporting source. As can be seen, the location remained the same 4 out of 5 times the asset identification data was collected. However, as shown in cell 3220, the generator was in a different position on August 29, 2006 at 7:37pm than before.

In one embodiment, the asset discovery notification module 2980 is used to provide notification when the identification data of the tagged asset has been populated into the database. For example, assume a building manager searches for generator 3173 on August 22, 2006, and cannot find it at or near latitude 38.1637/longitude 95.3221. He then uses the found asset notification module 2980 to flag the generator asset 3173. In one embodiment, when the subsequent identification data for the generator 3173 is populated into the database 205, the found asset notification module 2980 generates a notification, which is then published, for example, to the building superintendent's cell phone. The notification indicates that, for example, on August 29, 2006, identifying data for the generator asset was collected at a location of latitude 38.9886/longitude -95.3029. The building manager can then go to this location to search for the generator 3173.

It should be appreciated that the location information collected and reported is the actual location information associated with the reporting source (eg, reporting source 208A). However, due to the short range of the short-range communication devices (e.g., 3101, 3102, and 3103), the location information is accurate enough to facilitate locating the asset, or pointing the location of the asset to a particular construction site, construction site A portion, area of the leased premises, or specific area of the assigned property. This may be useful when trying to locate a lost or misplaced asset, when determining what asset is on a particular construction site, or on a particular leasehold. Therefore, this location information is sufficient for the building supervisor to realize that Generator Asset 3173 has been left on the old job site, misplaced behind a pile of trash, or hidden among some tall vegetation that has grown around it.

Referring now to FIG. 33, a block diagram of an exemplary GUI display 360B for an asset information report generated by an asset management system is shown, in accordance with one embodiment of the present invention. GUI display 360B is similar to GUI display 360 of FIG. 5 . In one embodiment, asset information report 360B includes asset 540 , asset column 510 , information source column 508 , map section 520 , and user toolbar section 530 . In general, the user toolbar portion 530 provides a way for the user to interact with the asset information report 360 . Map section 520 is automatically provided by property information report generator 750 as part of property information report 360B. Furthermore, elements 508 , 510 , 520 , 530 , and 540 have been previously described and are consistent with the previous description of similar elements thereof shown and described in connection with FIG. 5 .

Area 550 is a geo-fenced area, which in this example may be considered equivalent to construction site 3100 shown in FIG. 31 . Geofence area 550 covers map portion 520 and displays, for example, all assets that were last recorded as being located within geofence area 550 . Thus, asset 540 , asset 3171 , asset 3172 , and asset 3173 are displayed within geofenced area 550 . In this example report, the location of asset 550 has been actively reported via reporting source 208 . Meanwhile the reported locations of assets 3171, 3172 and 3173 have been tracked on an interim basis by the interim asset tracking methods and systems described above. The information displayed in the GUI allows awareness and management of assets located in areas designated by users (such as building supervisors, rental equipment managers, etc.).

Accordingly, embodiments of the present invention provide interim asset tracking systems and methods. Embodiments further provide automated methods of notifying and reporting asset-identifying information collected on an ad-hoc basis. Such ad-hoc tracking addresses the high costs typically associated with tracking assets by utilizing existing reporting sources in conjunction with near field communication devices to provide secondary (ad hoc) reporting capabilities, which can utilize existing asset management systems and infrastructure.

Part IX: Integrated Asset Management

overview

Embodiments described herein provide systems and methods for integrated asset management. In general, implementations described herein utilize multiple disparate sources to monitor information about an asset, such as location and operational information about the asset. Information from these unrelated sources is populated into the database. Verification information is also received from one or more enabled devices, such as WiFi (Wireless Fidelity) wireless Internet/network enabled devices or Bluetooth enabled devices, and populated into the database.

In some embodiments, such enabling devices communicate with client information systems (such as rental information systems, inventory information systems, maintenance Information systems, etc.) coupling. Such enabling devices are often hand-held and may include personal digital assistants, computers, etc., which may additionally be coupled to a printer. In some embodiments, such enabling devices are primarily used to report "inspection information" that is collected manually with the device (such as by reading a barcode on the asset or taking a picture of the asset) or by a human being. information manually entered into the device after inspection. For example, following a visual inspection, a human operator may note visible asset damage, visible maintenance issues, overall asset cleanliness, or other similar visually observable characteristics and then enter inspection information into an enabling device, which enables The functional device then uploads the inspection information to the client information system. In some embodiments, such an enabling device also receives asset data from a client information system. Many such enabling devices are known in the art.

Asset information and asset inspection information are populated into the database such that all or part thereof and any other information associated with the asset can be collected from the database in an integrated manner for use by the client information system or by the enabling device. In one embodiment, this includes providing a customized abstraction of data about the asset in a format usable by one or more enabled devices. In one embodiment, this includes providing a customized abstraction of data about the asset in a format usable by one or more client information systems. Data about the asset can be imported back to the enabling device or client information system that provided the verification information to the database, or back to another client information system or enabling device. In one embodiment, reports may also be generated from asset information, asset inspection information, and any other information associated with the asset and stored in the database.

Integrate asset management information

Referring now to FIG. 34 , an exemplary asset management system 700 is shown in conjunction with a first reporting source 208A, a second reporting source 208B, an optional first client information system 3405A, and an optional The second client information system 3405B is communicatively coupled. As shown in FIG. 34, the asset management system 700 is also communicatively coupled to a first enabling device 3409A and a second enabling device 3409B via a first client information system 3405A. To report inspection information about an asset to a client information system, an enabling device is a device that is communicatively coupled to the client information system, such as by a WiFi Internet or network link, Bluetooth link, or similar wireless coupler . Likewise, in some embodiments, such an enabling device also receives information about the asset from a wireless coupler coupled to the client information system.

Asset management system 700 includes data transceiver 330 , database 205 and optional asset information report generator 750 and optional integrated data transceiver 3480 . In general, data receiver 330 is configured to receive information about assets from multiple reporting sources, such as sources 208A and 208B. Data receiver 330 reports this asset information to database 205 using a first portion of information about the asset from first reporting source 208A, a second portion of information about the asset from second reporting source 208B, and other information reporting information about the asset. Information such as reporting sources populates the database 205 . Also, database 205 may similarly receive and maintain information for multiple assets. The specific functions and operations of data sinks 330 and database 205 with respect to asset information reporting sources (e.g., 208A and 208B) have been previously described, and, except where necessary to identify any differences or features not previously described, are not described here for the sake of brevity. Re-described here.

To provide integrated asset data extracted from database 205 and formatted by asset information report generator 3405A and also to receive asset survey information, optional integrated data transceiver 3480 is configured to communicate with client information systems such as optional client terminal information systems 3405A and 3405B). Client information systems (eg, 3405A and 3405B) are, for example, asset maintenance information systems, asset inventory information systems, asset leasing information systems, and the like. Typically, a client information system is not simply a client application (such as a spreadsheet), but instead (such as from external enabling devices 3409A and 3409B) receives information input and problem reports (such as receipts, job orders, inventory list, etc.) system.

Referring now to FIG. 35 , a flowchart of an exemplary method 3500 is shown for integrating asset management information according to one embodiment of the present invention. Elements of method 3500 will be described with reference to FIGS. 34 and 36 . 36 is a block diagram of an exemplary asset 3620 being returned to a leased location 3600 of an asset leasing company, according to one embodiment of the invention. Also, for purposes of example and not limitation, client information system 3405A of FIG. 36 will be described as a leased property information system. However, it should be understood that the concepts illustrated by this example implementation are applicable to other client information systems, such as inventory control information systems, maintenance information systems, payroll information systems, and the like.

Referring now to 402 of FIG. 35 and FIGS. 34 and 36 , one embodiment receives information about an asset from a first reporting source. As previously described, various reporting sources 208 may provide asset information about assets. By way of example and not limitation, the asset may be considered to be a dump truck 3620 leased from the rental facility 3600 and equipped with the first reporting source 208A. Typically, received information from reporting source 208A includes location and/or operational information regarding dump truck 3620 . Element 402 and reporting source 208A have been described previously and are not re-described here for the sake of brevity. Instead, reference is made to these previous descriptions.

Referring now to Figure 35 at 404 and Figures 34 and 36, one embodiment receives information about assets from a second reporting source. As previously described, various reporting sources 208 may provide asset information about assets. By way of example, reporting source 208B may be thought of as a portable computer used to enter information about dump truck 3620 while on-site maintenance is performed on asset 3620 by a rental company maintainer during the lease term. Typically, the received information includes location and/or operational information about an asset (eg, asset 3620). Element 404 and reporting source 208B have been described previously and are not re-described here for the sake of brevity. Instead, reference is made to these previous descriptions.

Referring now to 3506 of FIG. 35 and FIGS. 34 and 36 , one embodiment receives verification information about an asset (in this example, a dump truck 3620 ) from a first enabling device 3409A. By way of example and not limitation, it may be assumed that the first client information system 3405A as shown in FIG. 36 is an asset leasing information system. When the asset (such as the dump truck asset 3620) is returned to the rental site for inspection after the lease period ends, the client information system 3405A is populated with survey information received from the WiFi-enabled device (eg, the first enabling device 3409A). In another embodiment, the enabling device 3409A is a Bluetooth enabled device. In one embodiment, for example, the leasing agent uses the enabling device 3409A to perform a comprehensive condition inspection (such as cleanliness or Existence of damage) and input the results of the test into the enabling device 3409A, test the dump truck 3620 for any maintenance issues (such as visible maintenance issues like oil spills) and input the results into the enabling device 3409A and/or input Work orders for the dump truck 3620 (such as any cleaning or unscheduled maintenance needs noted during asset inspections) to gather investigative information about the asset (such as the dump truck 3620).

Thus, inspection information may include information such as a digital photograph of the asset, unscheduled work order requirements for the asset (e.g., based on damage, cleanliness, or maintenance issues noted during the inspection of the asset), or reporting some other visual observation about the asset received information. In one embodiment, the reported survey information is sent from the enabling device 3409A to the client information system 3405A, and from the client information system 3405A to the integrated data transceiver 3480, which populates the survey information into In a database (such as database 205). In another embodiment, the survey information is sent from the enabling device 3409A to the integrated data transceiver 3480, which populates a database (such as the database 205) with the survey information.

Similarly, a second enabling device 3409B is used in one embodiment to report survey information about an asset, such as asset 3620 . In one embodiment, the survey information is the same or similar survey information reported by the enabling device 3409A. In one embodiment, the second enabler 3409B reports additional survey information, such as the completion of a job order for an asset. For example, in one embodiment, enabling device 3409B is configured to report the completion of cleaning asset 3620 in response to a job command to clean asset 3620 . In one embodiment, the reported survey information is sent from the enabling device 3409B to the client information system 3405A, and from the client information system 3405A to the integrated data transceiver 3480, which populates the survey information into In a database (such as database 205). In another embodiment, the survey information is sent from the enabling device 3409B to the integrated data transceiver 3480, which populates a database (such as the database 205) with the survey information. While only two enabling devices 3409A and 3409B are shown in Figures 34 and 36, it should be understood that multiple such enabling devices (3409A...3409n) may report survey information about an asset in the manner described above.

Referring now to 3508 of FIG. 35 and FIGS. 34 and 36, one embodiment populates a database (such as a database 205), so that the information from the first reporting source 208A, the information from the second reporting source 208B and the inspection information from the first enabling device 3409A can be collected from the database in an integrated manner to be used by the client information system (such as the client Information system 3405A) used. In one embodiment, this includes storing information from the first reporting source 208A, information from the second reporting source 208B (along with any other asset information) and survey information from enabling device 3409A (along with any other asset survey information from other enabling devices). As previously described, this may include storing classification information in a single database 205 or in multiple databases that may be accessed together,

Generally, asset information report generator 750 is configured to be communicatively coupled with database 205 to generate asset information report 360 from asset data provided from database 205 . Asset information report 360 may include asset information reported from sources such as reporting sources 208A and 208B. Likewise, the asset information report 360 may also include inspection information, such as a digital photograph of the asset, record visual information about the asset record, or other inspection information reported from enabling devices such as 3409A and 3409B. In one embodiment, the asset information report generator 750 generates an asset that includes at least a portion of the information from the first reporting source 208A, at least a portion of the information from the second reporting source 208B, and at least a portion of the verification information from the first enabling device 3409A. Information Report 360.

An example of such an asset information report 360 is a comprehensive maintenance report that lists scheduled maintenance due based on hours of use reported by reporting source 208A and miles driven by reporting source 208B along Unscheduled maintenance required for visual inspection results. The operation of asset information report generator 750 in relation to generating asset information report 360 has been described previously and will not be re-described here for the sake of brevity.

Referring now to FIG. 37 , a flowchart of an exemplary method 3700 is shown for providing integrated asset management information according to one embodiment of the present invention. Elements of method 3700 will be described with reference to FIGS. 34 and 36 .

Referring now to 3702 of FIG. 37 and FIGS. 34 and 36, one embodiment accesses information about an asset received from a second reporting source 208B with information about an asset (such as a dump truck 3620) received from a first reporting source 208A. and the database 205 populated with verification information about the asset received from the first enabling device 3409A. For example, in one embodiment, asset information report generator 750 is communicatively coupled to database 205 and queries and extracts information about the Integrated asset data for assets such as dump trucks 3620. In one embodiment, the custom reporting module (previously described) of the asset information report generator 750 is used to conduct customized asset data queries and format integrated asset data for access by anticipated client information systems or enabled devices. The extracted integrated asset data is intended to be consumed by a client application, such as client application 3405A or 3405B. In various embodiments, a portion of the aggregated data that is accessed includes: a digital photograph of the asset, results of a full inspection of the asset, job order requirements for the asset, job order completion reports for the asset, visual inspection information recorded for the asset, leases for the asset Contract information (overtime, time of day, time of use, day or days of use, location of use or other such information), location information of the asset (current or past) and/or operational information of the asset.

Referring now to 3704 of FIG. 37 and FIGS. 34 and 36 , one embodiment updates a client information system, such as client information system 3405A or client information system 3405B. For example, in one embodiment, asset information report generator 750 supplies access data to integrated data transceiver 3480, which couples the access data to a customer information system, such as 3405A or 3405B.

In one embodiment, for example, integrated data about the asset is used to provision additional lease contract information after the asset is returned. Rather than just enabling an operator or agent to print a receipt (as many current systems are able to do), the integrated asset data provided includes rental contract information that allows the operator or agent to determine whether the terms of the rental contract are being followed. For example, consider the situation where a dump truck 3620 is leased for use on a Saturday in a particular state (such as Kansas) that is properly licensed and registered. Also, consider that the asset leasing company is closed on a Sunday, and after ten hours of use in Missouri on Sunday, the asset is returned first thing the following Monday morning. Investigation information, such as the date and time the asset was returned, is reported via an enabling device, such as the first enabling device 3409A. This survey information is added to database 205 . The asset information report generator 750 then extracts the integrated asset data about the lease contract and provides it back to the first enabling device 3409A via the client information system 3405A to help complete the lease contract accurately and quickly.

For example, in one embodiment, the synthetic asset data provided includes lease contract information derived from information received from an enabling device (such as 3409A) or a client information system (such as 3405A), such as lease terms (settlement date, return date etc). In one embodiment, the integrated asset data also includes lease contract information, such as lease contract information extracted from asset information provided by reporting sources, such as reporting sources 208A and/or 208B, such as asset operating information and asset location information. In one embodiment, additional property data, such as contract details, is supplied by the client information system 3405A. Based on this integrated asset data related to rental contract information, the rental agent may determine that dump truck 3620 was used in Kansas for eight hours on Saturday and ten hours in Missouri on Sunday. This would allow the rental agency to properly adjust fees for additional days of use and, if necessary, increase penalties for operating dump truck assets in Missouri in violation of the terms of the rental contract. This illustrates an example of how asset data collected from disparate sources and devices can be integrated and utilized by asset management system 700 to increase asset managers' awareness of asset usage days, hours of usage, and location.

In another example, in one embodiment, integrated data about an asset is used to supply a comprehensive job order that integrates both planned and unscheduled maintenance due for the asset. The composite job command is used to update the maintenance information system, which is the system 3405B shown in FIG. 34 for example. In such an embodiment, data for unscheduled maintenance comes from inspection data reported by an enabling device, such as enabling device 3409A, and data for planned maintenance comes from operational information reported by a reporting source, such as reporting source 208A (operating hours, engine time, oil level, etc.). Thus, in one embodiment, survey information received via the first client information system 3405A is integrated with other asset data that may be extracted from the database 205 to provide updates to the second client information system 3405B. This allows data to be shared between client information systems, which in many cases would not normally share data. This data sharing increases the efficiency and streamlining of companies such as asset leasing companies, asset maintenance companies, asset sales companies, or asset operating companies, among others.

In one embodiment, asset information report generator 750 is communicatively coupled with integrated data transceiver 3480 and transmits integrated data about the asset to a client information system (such as client information system 3405 or client information system 3405B). In one embodiment, asset information report generator 750 formats integrated data about assets for use by a client information system, such as client information system 3405A or client information system 3405B. In one embodiment, this includes an electronic format compatible (readable and usable) with a client information system (such as 3405A) and/or its enabling devices (eg, enabling devices 3409A and 3409B). In one embodiment, asset information report generator 750 formats integrated data about assets for use by enabling devices such as, for example, enabling devices 3409A and 3409B. In such an embodiment, this includes formatting any data and/or graphics such that they are displayed and/or printed with or by the enabling device 3409A and/or utilized or by the enabling device 3409B. In one embodiment, for example, the custom reporting module (described earlier) of asset information report generator 750 is utilized to extract integrated data about assets from database 205 and also customize the integrated data to be usable by, for example, a client information system such as 3405A or 3405B) or the format used by the enabling device (such as 3409A or 3409B).

Accordingly, embodiments of the present invention provide systems and methods for gathering and integrating asset management information that may include various asset information from multiple reporting sources and various asset inspection information from multiple enabled devices. Embodiments also provide a method of populating this gathered information into a database, such as database 205 . Embodiments also include systems and methods for providing integrated asset data updates to client information systems and for providing integrated asset data reports, both from assets stored in and accessed from a database information, asset inspection information, and any other asset data.

As can be seen, the methods and systems described above in connection with the asset management system 700 reduce or eliminate the need for overlapping processes, overlapping data collection, and disparate customer Inefficiency caused by terminal information systems. This reduces information bottlenecks and increases management awareness of the operation, location and availability of assets.

Part X: Detecting Construction Equipment Assets Process Going Wrong

overview

Asset location and operational information stored in database 205 can be analyzed and utilized for a number of purposes. One purpose is to detect and report construction equipment asset process errors. The term "process error" refers to the use of an asset to perform a process so that another asset or combination of assets can be performed more economically, efficiently or quickly; or the inappropriate use of the correct asset in performing the process. In the embodiments described below, process errors are managed by complying with one or more process specifications assigned to a construction equipment asset or assets.

Process error conditions may be corrected by detecting information in database 205 that indicates violations of process specifications and by reporting process errors in real-time or near real-time. Similarly, delayed reporting of process errors also allows construction managers to determine inappropriate usage of construction equipment assets, efficient and inefficient usage patterns of construction equipment assets, and efficient and inefficient usage patterns of workers operating specific construction equipment assets. Corrective actions, such as operator retraining, asset reconfiguration, or alternate asset usage, can then be taken to reduce future process errors.

The overall result of detecting and reporting construction equipment asset process errors is a reduction in such process errors. As a result, asset handling companies such as, for example, material handling companies may save money, time, or both. While this process error detection can be applied to many types of construction equipment assets, it is particularly useful in the construction industry when applied to "material handling" type construction equipment assets including: Bulldozers, graders, excavators, backhoes, compactors, loaders, articulated dump trucks, haul trucks, pavers, stacker and more.

asset management system

Referring now to FIG. 38 , a block diagram of an exemplary asset management system 700 is shown configured with an optional process error detector 3880 in accordance with one embodiment of the present invention. As shown in FIG. 38 , asset management system 700 includes data receiver 330 , database 205 , optional asset information report generator 750 and optional process error detector 3880 .

In general, data receiver 330 is configured to receive information about assets, such as location and/or operational information, from one or more sources 208 , such as sources 208A and 208B. The data receiver 330 reports this asset information to the database 205, which can then use the first portion of information about the asset from the first reporting source 208A, the second portion of information about the asset from the second reporting source 208B, and the reporting information about the asset. Such information from other reporting sources populates the database 205 . Also, database 205 may similarly receive and maintain information for multiple assets. Optional asset information report generator 750 is configured to communicatively couple with database 205 for generating asset information reports 360 from asset information data provided from database 205, and in some embodiments, asset information reports 360 are coupled to connected to the client application.

Asset management system 700 and many of the components shown in FIG. 38 have been previously described in detail. For example, first reporting source 208A, second reporting source 208B, data sink 330, database 205, optional asset information report generator 750, and optional reporting 360 have all been previously described. These previously described components operate in a manner consistent with their previous descriptions, and are therefore not re-described for the sake of brevity, except where necessary to point out additional features or methods of operation not previously described.

In one embodiment, optional process error detector 3880 monitors asset information stored in database 205 and compares the monitored asset information to one or more process specifications assigned to construction equipment assets. Through this comparison, the process error detector 3880 detects whether a process error has occurred for the construction equipment asset. Process error detector 3880 automatically detects process errors of assets, such as: incorrect construction equipment asset selection for a task; incorrect construction equipment asset operation when performing a task; and incorrect process execution when performing a task. Process error detector 3880 performs this automatic detection by detecting outliers from assigned process specifications resulting from combining and processing asset location information, asset operation information, and time information to determine whether a construction equipment asset is in violation of the asset's assigned process Operated in a standardized manner.

In various embodiments, the location information includes two-dimensional or three-dimensional positioning information, and in some embodiments, the positioning information also includes the orientation of the construction equipment asset. The location information originates from one or more positioning sensors, such as Global Navigation Satellite System (GNSS) receivers (eg, GPS, GLONASS, and/or Magellan), optical-based positioning information, laser-based positioning information, or some combination. The location information is received from one or more reporting sources 208 (described previously). The location information may be combined with operational information (described below) to determine, for example, the cycle distance for propulsion, hauling, or other transportation of some loads.

Operational information is gathered from sensor information received from one or more reporting sources 208, which in this embodiment report data from sensors installed on construction equipment assets. Thus, from such sensors, asset operational information is such as, for example, speed, heading, event data (e.g., loading, unloading, bucket angle, blade positioning, and other such operational event data) and/or engine safety / Machine safety data (eg, oil pressure, oil temperature, engine rpm, hydraulic fluid pressure, etc.).

In one embodiment, time information is gathered from database 205, such as from a time stamp sent along with the operational and location information. In one embodiment, the process error detector 3880 derives temporal information by combining location and operational information in some manner that determines temporal information. Time information includes data such as cycle time, loading time, unloading time, time between loading and unloading, idling time, pause time waiting for loading or unloading, elapsed time performing tasks, total operating time, and the like.

In one embodiment, process error detector 3880 generates process error report 3860 upon detection of a process error. In one embodiment, if a process error is detected, a process error report 3860 or some other notification is sent to the receiving device 3890 . This is used to notify administrators, supervisors, asset operators, etc. of process errors (and, if necessary, recommended solutions) so that process errors can be corrected. In one embodiment, the process error detector 3880 includes an operation specification module 3884 , a site specification module 3885 , a global specification module 3886 and a notification module 3887 .

In one embodiment, the operating specifications module 3884 derives one or more operating specifications for the construction equipment asset from observed asset information collected about the construction equipment asset or similar construction equipment assets and stored in the database 205 . The exported operating specifications are then manually or automatically assigned to construction equipment assets. An example of such an operating specification is the average cycle time required for a backhoe to collect a large volume of material on a particular job site. Another example of operational norms is the average pause time of dump trucks while waiting in the loading area of a job site.

Process Error Detector 3880 compares asset information stored in database 205 to such operating specifications to determine whether a construction equipment asset is being operated in a manner sufficiently inconsistent with operating specifications. If so, then a process error is detected by the process error detector 3880 . In one embodiment, triggering process errors are determined automatically by the operating specification module 3884 (e.g., based on a preset percentage of change from operating specification, a change outside a defined margin near the operating specification, or a predefined statistical change from operating specification) A change in the self-operating specification of the detection. In one embodiment, the change from operational specification that triggers detection of a process error is selected by a user of the asset management system 700 .

In one embodiment, the site specifications module 3885 includes one or more job site specific specifications assigned to construction equipment assets. Site-specific specifications are typically entered by a user of the asset management system 700 and are based on the tasks to be performed on the job site and specific knowledge of materials, conditions, topography, special needs, etc. that are unique to a construction site. An example of such a site specification is the average cycle time between loading and unloading of a dump truck. For example, this time may be longer than normally expected due to extremely wet conditions on the job site. Another example of an operating specification is the optimum swivel range for an excavator digging material from a steep hillside job site.

Process Error Detector 3880 compares asset information stored in database 205 to such site specifications to determine if a construction equipment asset is being operated in a manner sufficiently inconsistent with site specifications. If so, then a process error is detected by the process error detector 3880 . In one embodiment, an error in the triggering process is determined automatically by the field specification module 3884 (e.g., based on a preset percentage of variation from the field specification, a variation outside a defined margin near the field specification, or a predefined statistical variation from the field specification) The detection of changes from the site specification. In one embodiment, the change from site specification that triggers detection of a process error is selected by a user of the asset management system 700 .

In one embodiment, the global specification module 3886 includes one or more global specifications assigned to construction equipment assets. Generally, a global code is a code or common standard defined or commonly understood by the construction industry or some sub-sector of the construction industry to denote the proper use and/or operation of construction equipment assets. Typically, such global specifications are outlined and published by industry associations and construction equipment asset manufacturers and depend on factors such as: machine selection for a particular process, work tool selection, soil/material type and surface condition of the site in which the process is performed. An example of such a global specification is the optimum push distance for a bulldozer. Another example of a global specification is the optimum revolutions per minute (RPM) for a shovel's engine when the shovel is loading or unloading a particular type of material.

Process error detector 3880 compares asset information stored in database 205 to such global specifications to determine whether a construction equipment asset is being operated in a manner sufficiently inconsistent with the global specifications. If so, then a process error is detected by the process error detector 3880 . In one embodiment, an error in the triggering process is determined automatically by the global specification module 3885 (e.g., based on a preset percentage of change from the global specification, a change outside a defined margin near the global specification, or a predefined statistical change from the global specification) The detection of changes from the global specification. In one embodiment, the change from the global specification that triggers the detection of a process error is selected by a user of the asset management system 700 . In various embodiments, the global specification may be entered manually by the user into the global specification module 3886, selected from a list of global specifications available within the global specification module 3886 for a particular building equipment asset or asset type, or selected from some of the global specification modules. External repositories are referenced manually or automatically.

In one embodiment, notification module 3887 communicatively couples or issues optional process error report 3860 to receiving device 3890 after a process error is detected by process error detector 3880 . Receiving devices 3890 may include devices such as, but not limited to, telephones, cellular telephones, personal digital assistants, pagers, two-way radios, computers, computer networks, web pages, and email accounts. The notification module 3887 sends out the process error report 3860 in a format appropriate for the particular receiving device 3890 to which the process error report 3860 is sent. Thus, in various embodiments, the notification module 3887 can be configured to include: voice (such as a canned message), synthesized speech, text, email, HTML (or equivalent), and video (such as a digital photo or video file) error report 3860 is issued.

Methods for detecting process errors

Referring now to FIG. 39 , a flowchart of an exemplary method 3900 is shown for detecting construction equipment asset process errors in accordance with one embodiment of the invention. Elements of method 3900 will now be described with reference to FIG. 38 . Although specific steps are disclosed in method 3900, such steps are exemplary. That is, embodiments of the present invention are well suited for performing various other steps of step recitation method 3900 or variations thereof. It should be appreciated that the steps in method 3900 may be performed in an order different from that presented, and that not all steps in method 3900 may be performed. All or part of what is described by method 3900 may be implemented using computer-readable and computer-executable instructions residing, for example, in a computer-usable medium of a computer system, such as, for example, computer system 100 (FIG. 1 ) or a similar device step.

Referring now to FIG. 39 at 3902 and FIG. 38 , one embodiment receives information about building equipment from a reporting source. It should be appreciated that in one embodiment, a reporting source (such as reporting source 208A and/or 208B or other similar reporting source 208 ) may report some combination of asset location information, asset operational information, and asset timing information for construction equipment assets. For example, location information may be the asset's coordinate location on a map or the location of the asset within a particular job site or geofenced area. The time information may be local time provided by reporting source 208, GPS time, or some other time. Also, in one embodiment, the time relates to an event, such as when the asset is loaded with material. Operational information may indicate whether the asset having its engine running is stopped, is moving, is moving at a particular speed, is being loaded, is being unloaded, is being operated in a particular mode, or similar operational information. As previously described, in various embodiments, reporting sources (such as reporting source 208A) include such as, but not limited to: TrimTrac ^™ devices, devices, mobile phones, video devices, personal digital assistants, portable computing devices, radio frequency identifiers, global navigation satellite systems (GNSS) and sources of human intelligence (HumInt). The function and operation of such reporting sources as 208A and 208B is consistent with the previous description of these reporting sources.

Referring now to FIG. 39 at 3904 and FIG. 38, one embodiment populates the database 205 with received asset information. This is consistent with the previous description of receiving asset information and populating the information into database 205 . For example, depending on the number of reporting sources from which database 205 receives information about the asset, database 205 may be populated with a first portion of information about the asset provided by first reporting source 208A and, if available, with information from a second reporting source. The second portion of information about the asset at 208B populates the database 205 and so on.

Thus, when such information is reported for an asset by one or more reporting sources (208A, 208B, . . . 208n), the database 205 stores therein a considerable amount of information about the asset's location(s), operation, and general usage. This is especially true when updates to asset information are received at short intervals, such as a few times per second, every second, every few seconds, or every minute, or some other short interval. As can be seen, this asset information can be used by the process error detector 3880 to determine the operational status of the asset, which includes: whether the asset is moving or stopped; the asset is being loaded or unloaded; how far or fast the asset is traveling or has traveled; when and where the material is loaded; how far the asset has traveled in a particular mode of operation (cycle distance); the angle at which the blade or bucket is positioned while performing the process, when and where the asset is loaded and unloaded with material and other such kind of information.

Referring now to 3906 of FIG. 39 and FIG. 38 , one embodiment provides a misuse report 3860 if a construction equipment asset is operating in violation of the process specification assigned to the construction equipment asset. An optional process error detector 3880 as shown in FIG. 38 adds asset process error detection and reporting functionality to the asset management system 700 . Process error detector 3880 is communicatively coupled with database 205 . While shown and described as a separate entity in system 700, it should be appreciated that in some embodiments some or all of the functionality of process error detector 3880 may be distributed among other entities (such as asset information report generator 750) or provided by Other entities execute.

In one embodiment, the process error detector 3880 automatically receives selected information from the database 205 regarding the location and/or operation of one or more particular construction assets that it is monitoring for process errors. In another embodiment, the process error detector 3880 queries the database 205 for selected information regarding the location, operation, or time related to the particular asset or assets it is monitoring for process errors. Typically, the selected information received or queried relates to one or more process specifications that have been assigned to the particular asset being monitored for process errors. Process error detector 3880 compares the selected information to one or more process specifications assigned to the asset. Process error detector 3880 generates process error report 3860 when, based on the comparison, the selected information indicates a violation of the process specification assigned to the asset.

In one embodiment, one or more process specification modules (3884, 3885, 3886) are used to assign one or more process specifications to building equipment assets. The process specification assignments form the boundaries of the operating range of the construction asset. If the selected information from the database 205 indicates that the construction equipment asset is being operated within the confines formed by the process specification(s), then the process error detector 3880 deems the asset to be used properly and no process error report 3860 is generated. If selected information from database 205 indicates that the construction equipment asset is being operated outside of this range (in violation of one or more process specifications), then process error detector 3880 deems it appropriate to generate process error report 3860 .

Example of process error detection

In one embodiment, for example, process error detector 3880 monitors bulldozer assets for optimal push/haul distances. The process error detector 3880 monitors the asset location and operational information in the database 205 regarding the push/haul distance of the bulldozer asset. This information is compared to a specification (such as a field specification or a global specification) indicating that the optimal push/haul distance for this bulldozer is in the range of 10 meters to 90 meters. If the bulldozer violates this process specification (eg, if the average push/haul distance for 10 consecutive push/hauls is 130 meters), then the process error detector 3880 generates a process error report 3860 for the bulldozer. In one embodiment, process error report 3860 includes recommendations, such as switching to a different asset (eg, a shovel). This particular embodiment is an example of generating a process error report 3860 when the process error detector 3880 determines that a construction equipment asset, in this case a bulldozer, is the incorrect asset for performing a particular process according to the assigned process specification. . In one embodiment, the notification module 3887 sends a process error report 3860 to the receiving device 3890 .

In one embodiment, for example, the process error detector 3880 monitors the excavator asset for optimal swivel angle during extensive digging/loading operations. Process error detector 3880 monitors asset location and operational information in database 205 regarding the swing angle of the excavator asset. This information is compared to a specification (such as an operating specification, a site specification or a global specification) for this process indicating that the optimum swing angle for this excavator is between 60 degrees and 90 degrees. If the excavator violates this process specification (eg, if the average swing angle for 15 consecutive iterations of the process is 50 degrees), then the process error detector 3880 generates a process error report 3860 for the excavator. In one embodiment, process error report 3860 includes recommendations, such as adjusting excavator settings or field settings. This particular embodiment is an example of providing a process error report when the process error detector 3880 determines that a construction equipment asset (in this case an excavator) has improperly performed a particular process according to the assigned process specification. In one embodiment, the notification module 3887 sends a process error report 3860 to the receiving device 3890 .

In one embodiment, for example, process error detector 3880 monitors the operation of excavators and trucks (or trucks) for proper loading cycle times. Process error detector 3880 monitors asset location and operational information in database 205 about excavator and truck assets. Process error detector 3880 also monitors and/or derives cycle time information and pause time information for excavator and truck assets from information extracted from database 205 . This cycle time information is compared to a specification (such as an operational specification, a site specification or a global specification) indicating that the optimal loading operation cycle time for this asset portfolio is, for example, 90 seconds. If the asset exceeds this cycle time by more than, for example, 15%, the process error detector 3880 generates a process error report 3860 for the bulldozer and/or truck. In one embodiment, process error report 3860 includes a recommendation to change the process. In one embodiment, the process error detector 3880 compares the cycle times of multiple trucks used in the process to determine if the cause of the process error can be determined. For example, if the process error detector 3880 indicates that the excavator is stalled due to a lack of trucks waiting to be loaded, then it is recommended that more trucks be added. Similarly, if the process error detector 3880 indicates that the excavator is stalled, but the truck is waiting to be loaded, then a recommendation to adjust the excavator or site settings is provided. In one embodiment, the notification module 3887 sends a process error report 3860 to the receiving device 3890 .

In another embodiment, for example, process error detector 3880 monitors the operation of excavators and trucks (or trucks) for proper loading cycle times. Process error detector 3880 monitors asset location and operational information in database 205 about excavator and truck assets. Process error detector 3880 also monitors and/or derives cycle time information and pause times for excavator and truck assets from information extracted from database 205 . This pause time information is compared to a specification (such as an operational specification, site specification, or global specification) that indicates that the optimal pause time for any asset during a loading cycle is zero (no truck or excavator waiting). Process error detector 3880 generates excavator and/or truck process error report 3860 if any asset experiences a pause time of, for example, more than 10 seconds in three consecutive loading cycles. In one embodiment, the process error detector 3880 includes a recommendation to change the process. In one embodiment, the process error detector 3880 compares the excavator's cycle time to determine if the cause of the process error can be determined. For example, if the process error detector 3880 indicates that the excavator requires more than 5 bucket cycles or an average of more than 100 seconds to load, then a larger excavator bucket is recommended. Similarly, if the process error detector 3880 indicates that the excavator is using the optimal number of bucket cycles to fill the truck, but the truck is waiting, then it is recommended to use fewer trucks. In one embodiment, the notification module 3887 sends a process error report 3860 to the receiving device 3890 .

In another embodiment, for example, process error detector 3880 monitors the operation of the shovel for improper use or poorly trained operators. Process error detector 3880 monitors asset location and operational information in database 205 about the scraper asset. For example, in one embodiment, a process error detector monitors the engine revolutions per minute (RPM) of a shovel in a particular mode of operation. In another embodiment, the process error detector 3880 also monitors and/or derives cycle time information and cycle distance information for the shovel asset from information extracted from the database 205 . This RPM information is compared to a specification (such as an operating specification, a site specification or a global specification) indicating that the optimal RPM range for the particular mode of operation of the shovel is 1700 RPM to 2200 RPM. Process error detector 3880 generates a process error report 3860 for, for example, a shovel if the shovel asset has an average engine RPM that deviates from this range by more than 10% over three operating cycles performing a particular process. In one embodiment, the process error report 3860 includes a recommendation to check the configuration of the shovel or retrain the operator. In one embodiment, the notification module 3887 sends a process error report 3860 to the receiving device 3890 .

Consider FIG. 40 , which shows an exemplary construction equipment asset of a loader 4015 , dump truck 4020 , and scraper 4030 along with piles of material ( 4001 , 4002 , and 4003 ) on the job site. Site map 4000 is not drawn to scale, but as shown, stack 4002 is greater than 100 meters and less than 3000 meters away from stack 4001 . Furthermore, as shown, stack 4003 is greater than 3000 meters away from stack 4001 .

To be efficient, the global specification module 3886 has assigned a maximum average load cycle distance of 3000 meters to the scraper 4030 as the global specification. Thus, if the average load cycle distance of the backhoe 4030 exceeds 3000 meters for any number of loads (eg, three loads), the process error detector 3880 will generate a process error report 3860 . Similarly, for efficiency, the site specification module 3885 has assigned a minimum average loading cycle distance of 3000 meters to the dump truck 4020 as the site specification. Thus, if the minimum load cycle distance of the dump truck 4020 drops below an average of 3000 meters for any number of loads, such as five loads, the process error detector 3880 will generate a process error report 3860 . Additionally, based on the data collected in database 205 , operating specification module 3885 has assigned a maximum loading cycle distance of 100 meters to loader 4015 as an operating specification. Thus, the process error detector 3880 will generate a process error report 3860 if the maximum load cycle distance of the loader 4015 exceeds 100 meters when the loader 4015's bucket is loaded with material.

In general, there are three methods that construction assets 4015 , 4020 , and 4030 may use to move material from pile 4001 to pile 4002 or to pile 4003 . One approach is to use the scraper 4030 to load material at pile 4001 and then drive to pile 4002 or 4003 to have the scraper 4030 unload the material. Another method is to use the loader 4015 to scoop material from the pile 4001 into the dump truck 4020. The dump truck 4020 will then drive to the pile 4002 or 4003 and dump the loaded material. Yet another method is to load material from pile 4001 into the hopper of loader 4015 and unload material at pile 4002 or 4003 . Where a large amount of material needs to be moved from pile 4001, the material may be moved utilizing loader 4015, dump truck 4020, scraper 4030, or some combination thereof, with tens, hundreds, or thousands of loads. With construction companies performing this type of job facing thin margins and tight deadlines, it becomes very important to use the correct asset or combination of assets to perform material handling tasks in the most efficient manner possible.

Thus, in this example, since moving material from pile 4001 to pile 4002 or to 4003 would require loader 4015 to travel more than 400 meters in the loading mode of operation, if loader 4015 is used to move material from pile 4001 to stack 4002 or moved to 4003, then the process error detector 3880 will generate a process error report 3860. Similarly, if dump truck 4020 is used to move material five or more times between piles 4001 and 4002, process error detector 3880 will generate process error report 3860, but dump truck 4020 is used to move the material from When the pile 4001 is moved to the pile 4003, the process error report 3860 will not be generated. Finally, if the scraper 4030 is used to move material from the pile 4001 to the pile 4003 (in more than three loading cycles), the process error detector 3880 will generate a process error report 3860, but when the scraper 4030 is used to transfer When material is moved from pile 4001 to pile 4002, process error report 3860 will not be generated.

process error report

In one embodiment, the generated process error report 3860 is saved by the process error detector 3880, such as to a computer memory or hard drive that can be accessed by the user immediately or after some time. In one embodiment, notification module 3887 communicatively couples or issues process error report 3860 to receiving device 3890 .

Referring now to FIG. 41 , an exemplary process error report 3860A is shown displayed on an exemplary receiving device 3890A, according to one embodiment. In FIG. 40, exemplary process error report 3860A includes an email message that was sent to personal digital assistant 3890A. Following the example of Figure 40, Process Error Report 3860A indicates that Shovel 4030 is operating at a cycle greater than the 3000 meter average. In another embodiment, process error report 3860A also includes a recommendation, such as using a dump truck/excavator combination instead of a backhoe. Process error reporting 3860A via, for example, wired or wireless means such as a wired or wireless coupler between receiving device 3890A and a computer network or the Internet or a wired or wireless coupling between receiving device 3890A and a radio, pager, or cellular telephone network. coupler) to the receiving device 3890A.

Issuing a process error report (e.g., process error report 3860A) to a receiving device (e.g., receiving device 3890A) can provide a means for real-time, near-real-time, or post-event notification of process errors to individuals, such as construction foremen, supervisors, administrators Or even equipment operators. This provides information to responsible parties that a particular construction equipment asset, such as the scraper 4030 , was improperly used in some manner that violated the established specifications of the construction equipment asset. In the case of real-time or near-real-time notifications, the rapid delivery of process error reports (such as process error report 3860A) by notification module 3887 provides an opportunity for process error situations that need to be resolved quickly so that the possibility can be mitigated or otherwise resolved Economic loss or inefficient use of assets.

Accordingly, embodiments of the present invention provide methods and systems for detecting and reporting process errors in the use of construction equipment assets. Embodiments also provide methods and systems for assigning one or more process specifications to construction equipment assets. Embodiments also provide for delivering or "emitting" asset process error reports to various receiving devices in a format appropriate for the particular receiving device to which the process error reports are being sent.

The disclosed methods and systems also allow a company or individual to ensure that appropriate construction equipment assets are being used to perform tasks and that, in performing tasks, the construction equipment assets are being used appropriately or efficiently relative to assigned process specifications.

Part XI: Leveraging Historical Data in an Asset Management Context

overview

Asset location and operational information stored in database 205 of FIG. 7 can be analyzed and utilized for a number of purposes. One purpose is to detect and report construction equipment asset process errors. The term "process error" refers to the use of an asset to perform a process so that another asset or combination of assets can be performed more economically or quickly, or the inappropriate use of the correct asset in performing the process. Process errors are governed by one or more specifications assigned to construction equipment assets.

The second purpose is to provide and implement planned maintenance capabilities. For example, when an asset is on-site, the asset's location and information stored in database 205 may provide the most recent status of the asset (such as time) since last maintenance, any issues with the asset, and the like. By monitoring asset location and operational information, management systems can schedule maintenance on specific assets based on actual utilization of the asset, rather than guesswork based on site time, etc.

In other words, rather than missing maintenance or taking unnecessary maintenance off of an underutilized asset from work because an asset is being used more frequently than expected, asset location and operational information can be used to ensure that maintenance is timely. Also, since the location of the asset is known, maintenance on the asset can be performed. Furthermore, because the operational information will provide time when the asset is not in operation or in a state of reduced operation, it is possible to determine a convenient time to perform maintenance.

In many cases, the asset location and operational information analyzed and utilized is real-time or near-real-time information. For example, when asset information is received into a database, it is quickly output in a reporting format that can be monitored by an asset management system (such as asset management system 700 of FIG. 7). In doing so, the asset management system 700 can provide an up-to-date overview of the asset, including location, operation, process errors, expected and unexpected maintenance needs, and the like.

However, in some cases, any or all flow of asset location and operational information may be impeded. For example, an asset reporting source, such as first reporting source 208A, may have transmission issues. That is, the transmitter may be in a non-receiving location, the battery may be dead, the first reporting source 208A may be damaged or destroyed, and so on. Thus, less information about assets will be received into the database. In some cases, this reduction may result in a portion of the asset management system 700 reporting 360 missing at least a portion of the information. For example, asset management system 700 may provide an up-to-date overview of assets including location information. However, due to the absence of the first reporting source 208A, expected or unexpected maintenance needs, etc. are no longer updated at the asset management system 700 .

Thus, it is not that the asset management system 700 simply maintains previous quantities until new information is received. That is, rather than miss any planned maintenance or other event because the counter has stopped counting, the asset management system 700 will recognize the lack of updated data. The asset management system 700 will then refer to the historical data extrapolator to provide operational information based on previously stored data. For example, if an asset has been operated 10 hours a day for the past 10 days, then the historical data extrapolator will provide daily operational updates for 10 hours so that no planned maintenance will be missed. Also, if an event is missed due to missing data, by providing extrapolation or location data, the asset management system 700 will be able to queue users who may have missed the event faster.

asset management system

In one embodiment, the embodiments described in this section are utilized in conjunction with the exemplary asset management system 700 communicatively coupled with the client application 710 of FIG. 7 . As described in detail herein, asset management system 700 includes data receiver 330 , database 205 , and asset information report generator 750 . Various embodiments of the functionality and operation of the asset management system 700 and its components have been described herein, and, except for the various alternative embodiments described with respect to the asset information report generator 750 described with respect to FIG. Repeat.

Referring now to FIG. 42, a block diagram of an exemplary asset information report generator 4250 is shown, according to one embodiment of the present invention. In one embodiment, asset information report generator 4250 includes data provider 4205 , historical data extrapolator 4210 , report generator 4220 .

In one embodiment, the data provider 4205 is configured to provide current data about the asset. Typically, current data refers to real-time or near-real-time data. In one embodiment, current data about the asset is received from a database, such as database 205 of FIG. 7 . Historical data extrapolator 4210 is configured to provide extrapolated data about assets based on historical asset data stored in database 205 .

Report generator 4220 is configured to generate asset information report 360 regarding at least one asset. For example, asset report generator 4220 uses asset information report 360 to extrapolate data about the asset when at least a portion of real-time data about the asset does not exist. As described herein, in one embodiment, extrapolated data about assets provided in asset information reports is used to trigger missed events. For example, extrapolated data about an asset provided in an asset information report can trigger a maintenance event.

Referring now to FIG. 43 , a diagram of an exemplary printable format 4300 of a custom asset information report 360 generated by an asset management system 700 incorporating an asset information report generator 4250 is shown in accordance with one embodiment of the present invention. As shown in FIG. 43, an asset information report with a customized title 4310 "Weekly Truck Usage Report" has been generated by a custom reporting module (such as custom reporting module 959A of FIG. 9).

Report 4310 has been formatted with information from the customized query for asset information on asset 540B (truck). The information is arranged into a customized structure of rows and columns, where each row represents structure 540B and each column represents asset-specific information about asset 540B. Column 601 represents the asset type. Column 4304 represents the day of the work week. Column 4306 represents the calendar date associated with a particular day of the work week. Finally, column 4308 represents the total number of hours that asset 540B was utilized during the particular day and date.

For example, this customized printable format 4300 is used by the maintenance department to plan maintenance. For example, a maintenance department may determine whether the number of hours an asset has been in operation corresponds to a maintenance interval. In this example, during the week, the asset has moved 37.7 hours along the maintenance interval. Additionally, in one embodiment, if an asset is down at the time of a scheduled maintenance call, the maintenance department can monitor the asset to ensure that scheduled maintenance is not missed. Although maintenance is described here, embodiments are well suited for any type of asset monitoring. The use of planned maintenance is only one of many possible asset monitoring possibilities and is provided here for simplicity only.

In one embodiment, the customized printable format 4300 also includes an hourly operation 4308 block 4335 . Generally, 4335 refers to a box populated with data extrapolated from historical information stored in database 205 . For example, all other data (eg, hours of operation Monday through Wednesday and Friday) is based on actual real-time data received by the asset management system 700 . However, the hours of operation on Thursday are not recorded, lost, destroyed or otherwise rendered unusable.

Rather than leaving block 4335 blank, historical data in database 205 is accessed by historical data extrapolator 4210 . Then historical data extrapolator 4210 reaches an extrapolation of 8.1 hours of operation for Thursday, August 17 and the information is provided to report generator 4220 causing the extrapolated information to end in report 4300 . By providing extrapolated results, the hours of asset operation are kept fairly precise. In other words, maintenance plans (or any other asset tracking information) will not be held up due to lack of asset operational data.

In general, historical data extrapolator 4210 can utilize a number of methods for generating extrapolated data. For example, extrapolated data may be based on an average of previous days of operation (eg, an average of the last 5 days of operation). In another embodiment, the extrapolated data may be based on an average of previous days of the same operation (eg, the average of the last 5 Thursdays of operation). In yet another embodiment, extrapolated data may be based on users utilizing the property (eg, Bob utilizes the property on average 8.1 hours a day) - which is also extrapolated based on the same operating days. In yet another embodiment, the extrapolated data may be based on weather (eg, the database indicates that Thursday is sunny, and the average asset usage for sunny days is 8.1). Also, the extrapolated data may be based on asset location (eg, the database indicates that the asset is in San Jose, where the average asset usage is 8.1).

Therefore, it is clear that extrapolation of historical data is limited only by one's imagination. In other words, the extrapolation can be based on any property in the database, a combination of two or more properties in the database, a combination of at least one property in the database and any other external information, and so on. Also, as the database grows, comparisons can be made between extrapolations and actual results that can then be added to the database to further refine the accuracy of the historical data extrapolator 4210 .

44 is a flowchart of an exemplary method for utilizing historical data in an asset management environment according to one embodiment of the invention.

Referring now to diagram 4402, an embodiment generates asset information report 360 from database 205, wherein asset information report 360 includes at least a portion of real-time information about the asset when the real-time information about the asset is available 4205. As described herein, in one embodiment, the real-time information is location and/or operational information about assets. In another embodiment, the real-time information is environmental status information.

Referring now to 4404, one embodiment augments asset information reporting 360 by extrapolating at least a portion of historical asset information 4210 stored at database 205 when at least a portion of real-time information 4205 is not available. As described herein, in one embodiment, the extrapolated information is location and/or operational information about an asset. In another embodiment, the extrapolated information is environmental condition information. Additionally, as described herein, in one embodiment extrapolated asset information is used to trigger missed events. That is, the addition of previously missing data may trigger a missed event flag provided by the asset management system 700 when the extrapolated data is entered into the report 360 . For example, if a maintenance call is due at the 800 hour mark and the addition of extrapolated data to the report 360 causes the asset to pass the 800 hour mark, then the 800 hour mark will be assumed to be exceeded and a missed event notification (eg, a maintenance event) may be triggered.

Accordingly, embodiments of the present invention provide methods and systems for utilizing historical data in an asset management environment. Embodiments also provide methods and systems for utilizing historical data in an asset management environment during real-time or near real-time operations. These methods and systems also provide companies or individuals with the tools to manage efficient and economical use of assets being operated, and also ensure that planned events are not missed indefinitely or unnecessarily rescheduled.

Part XII: Automatic Asset Classification

Embodiments of the invention include a system and method for automatically classifying assets. Typically, the reporting device accesses at least one asset characteristic (eg, asset VIN), reports the asset characteristic to an asset management system (eg, asset management system 300 of FIG. 3 ) and the asset manager automatically classifies assets based on the asset characteristic.

Asset characteristics to be used to classify assets include, but are not limited to, asset make-up, model number, serial number, year of manufacture, and other asset configuration details. The asset properties are used to automatically configure asset properties such as icon (graphical representation), delineation, name, maintenance intervals etc. enforced by the asset manager. Automatic classification and/or identification of assets is valuable to feature development and marketization of asset management systems because of their ease of use and implementation.

In one embodiment of the invention, an interface (eg, a communication interface or bus) of an asset is accessed to gather information about the asset (eg, asset characteristics). Location-based assets can query the asset and report asset characteristics to the asset manager. The asset manager can then interpret the asset characteristics (eg, decode the VIN, etc.).

When the asset manager receives new configuration information about the asset, the asset properties will be configured based on the asset properties. For example, make and/or model can be used to select a graphical representation (eg, icon) from a list to associate an asset with. In one embodiment, default names may be assigned to assets. For example, if the asset is a bulldozer, and there are already ten types of bulldozers registered in the asset management system, a new bulldozer can be assigned the default name of Cat D8R#11. Other useful information (eg, maintenance schedules) can be added to the asset-related delineation fields. In one embodiment of the invention, asset information is stored in a database associated with the asset manager.

One advantage of the present invention with respect to automatic asset classification is that many assets can be automatically configured (eg, on the fly), saving time and effort spent on managing assets. Additionally, the collected asset characteristics provide useful information to improve asset manager feature development and marketing. Furthermore, since reporting sources can easily move from one asset to another, it is important that the reporting device uniquely identifies the asset to which it is coupled to reduce the use of data tagged on different assets (e.g., information collected by the reporting device about asset data) possibility. For example, if the reporting device is moved from a bulldozer to a tractor, the reporting device should recognize that the asset has changed from a bulldozer to a tractor. This feature is especially useful for the asset leasing industry because it reduces the chance of misidentifying existing assets.

In one embodiment of the invention, automatic asset classification is performed when a reporting source is installed in an asset. For example, when a new asset is acquired, a reporting source can be installed to facilitate management of the asset. In one embodiment of the invention, the asset manager associates a particular reporting device (eg, device number) with a particular asset.

During the initial installation of a reporting device on an asset, it is important to establish the association between the reporting device and the asset type. For example, it is important to determine if the reporting device is attached to a truck, car, tractor, bulldozer, etc. Asset management becomes increasingly difficult if assets are not properly classified.

Embodiments of the present invention automatically classify assets based on at least one asset characteristic to improve asset classification and asset management. In one embodiment of the invention, the reporting device directly accesses asset characteristics (eg, vehicle identification number, etc.) from a communication system associated with the asset. Asset characteristics are then reported to the asset manager and the asset manager automatically determines asset classification and/or configuration based on the asset characteristics.

For example, if a vehicle identification number (VIN) is reported to the asset manager, the asset manager can decode the VIN or use the VIN (e.g., connect to a manufacturer database and look up the VIN) to retrieve other information about the asset (e.g., type, age, color, options, etc.), this information can help categorize assets. In one embodiment of the invention, graphical icons are automatically assigned to assets based on asset characteristics. Graphical icons may also include asset name and/or asset description fields.

FIG. 45A is an illustration of an exemplary reporting device 208 connected to an asset 4544. In one embodiment of the invention, reporting device 208 is communicatively coupled to asset 4544 and may interface with a communication system (eg, bus) associated with asset 4544 . In one embodiment of the invention, asset characteristics are automatically retrieved from asset 4544 or manually entered into reporting device 208 (eg, at installation time).

Figure 45B is a block diagram of an exemplary reporting device 208 according to an embodiment of the present invention. 2A, the reporting device 208 may be a permanently installed device 210, an asset installable/removable device 215, a portable computing device 220, a personal digital assistant 225, a smart phone 230, a mobile phone 235, a human intelligence (HumInt) 240 or any other device capable of accessing and reporting information to an asset manager according to embodiments of the present invention. For example, reporting sources 208 may include electronic devices, human sources, assets being monitored, other assets, and the like. In one embodiment, reporting source 208 can provide asset information including, but not limited to, location information, operational information, and status information and asset characteristics accessed from the asset itself or from any other source.

装置、射频识别器、全球导航卫星系统(GNSS)和类似装置。此外，报告源208可以包括若干种能力，诸如定位固定、摄影、视频/照片记录、文本传信、语音传信、数据传信和类似能力。此外，在一个实施方案中，报告源208可以进行资产操作监测。例如，报告源208可以通过输入4510耦接资产以监测资产特性4520，包括但不限于，J-BUS、控制器局域网总线(CAN-BUS)、与资产耦接的处理器、诊断评估器、发动机微处理器、里程指示器、速度表、转速计、油压指示器、轮压指示器、液压指示器、发动机定时监测器和类似特性。还应明白，输入4510可以包括供(例如)报告源安装人员手动输入资产特性的构件(例如，键盘、触摸屏、扫描装置等)。报告源也包括输出4530用于将资产特性4520提供给资产管理器数据接收器330(见图3)。In one embodiment, reporting device 208 may be a TrimTrac ^™ device,

devices, radio frequency identifiers, global navigation satellite systems (GNSS) and similar devices. Additionally, reporting sources 208 may include several capabilities, such as position fixation, photography, video/photo recording, text messaging, voice messaging, data messaging, and the like. Additionally, in one embodiment, reporting source 208 may conduct asset operation monitoring. For example, reporting source 208 may be coupled to the asset via input 4510 to monitor asset characteristics 4520, including but not limited to, J-BUS, Controller Area Network Bus (CAN-BUS), processor coupled to the asset, diagnostic evaluator, engine Microprocessors, mileage indicators, speedometers, tachometers, oil pressure indicators, wheel pressure indicators, hydraulic indicators, engine timing monitors and similar features. It should also be appreciated that input 4510 may include means (eg, keyboard, touch screen, scanning device, etc.) for manual entry of asset characteristics, eg, by a reporting source installer. The reporting source also includes an output 4530 for providing asset characteristics 4520 to the asset manager data sink 330 (see FIG. 3 ).

46 is a block diagram of an exemplary system for automatically classifying assets according to an embodiment of the invention. Reporting device 208 reports asset characteristics to asset management system 300, as described above. In one embodiment of the invention, reporting source 208 automatically reports asset characteristics to asset management system 300 . In another embodiment of the invention, the asset manager 300 prompts the reporting device 208 to provide asset characteristics and in yet another embodiment of the invention, the reporting source 208 periodically reports the asset characteristics to the asset manager 300 . It should be appreciated that asset manager 300 and reporting source 208 may communicate in any number of ways, such as wirelessly.

The asset characteristics are received by data receiver 330 . In one embodiment of the invention, database 205 is populated by asset properties. In one embodiment of the invention, reporting device identifiers (eg, reporting device numbers) are also stored in database 205 . In one embodiment of the invention, reporting means 208 is associated with an asset characteristic.

Asset classifier 4690 uses asset properties to assign specific asset classes to assets. It should be appreciated that any kind of asset classification can be assigned, for example, an asset classification can include asset type, age, manufacturer, asset owner, service information, and the like. It should be appreciated that asset identifier 4690 may retrieve other asset information from sources external to asset management system 300 , such as from network 4669 . It should be appreciated that network 4690 may include the Internet.

In one embodiment of the invention, asset classifier 4690 assigns graphical representations (eg, icons) of assets based on asset classifications. Graphical asset representation 4650 may be generated based on asset classifications determined by asset classifier 4690 . Graphical asset representations may then be provided to and presented on display 4660. It should be appreciated that display 4660 may be remote from asset management system 300 .

FIG. 47 is a flowchart of an exemplary method 4700 for automatically associating assets with graphical representations based on asset characteristics, according to an embodiment of the invention. In one embodiment of the invention, method 4700 is performed on asset management system 300 .

In step 4720, method 4700 includes receiving at least one asset characteristic from a reporting source. In one embodiment of the invention, asset properties are accessed directly from a control or communication system associated with the asset. For example, the VIN associated with an asset can be retrieved from the asset's CAN-BUS or J-BUS, however, it should be understood that asset characteristics can be retrieved in any number of ways. For example, the reporting device may include a scanner operable to scan information (eg, barcodes) associated with the asset.

In step 4730, method 4700 includes automatically associating the asset property with the graphical representation of the asset based on the asset property. For example, if it is determined that the asset is a tractor, step 4730 may assign a tractor icon to the asset. In one embodiment of the invention, a reporting device may be associated with an asset and/or a graphical representation of the asset.

At step 4740, method 4700 includes providing a graphical representation of the asset on a graphical user interface. In one embodiment, asset management is viewed on a graphical user interface. Automatically assigning appropriate graphical representations of assets facilitates asset management in accordance with embodiments of the present invention.

In one embodiment of the invention, the method 4700 further includes automatically configuring the reporting device and/or the asset manager based on the graphical representation associated with the asset in step 4730 .

In another embodiment of the invention, the reporting source is provided in response to feedback (eg, visual and/or audio) from the asset manager associating the asset with the graphical representation. For example, a green light may be emitted if the association is successful, and a red light may be emitted if the classification fails (and other asset characteristics are required).

In one embodiment of the invention, method 4700 includes populating the database with asset characteristics. For example, a database may be populated with reporting device identifiers and associated graphical representations.

48 is a flowchart of an exemplary method 4800 for automatically classifying assets according to an embodiment of the invention. At step 4820, method 4800 includes utilizing a reporting device associated with the asset to obtain at least one property of the asset. It should be appreciated that asset characteristics may be obtained directly from the asset or may be manually entered into the reporting facility.

In step 4830, method 4800 includes providing the asset characteristics to the asset manager. It should be appreciated that asset characteristics may be provided to the asset manager in any number of ways, including wireless communication.

In step 4840, method 4800 includes automatically determining an asset classification for the asset based on the asset characteristics. In one embodiment of the invention, asset characteristics are used to determine other asset characteristics. For example, from the VIN it is possible to determine the composition, year, etc. of the asset.

In one embodiment of the invention, the method 4800 further includes automatically configuring the reporting device and/or the asset manager based on the asset classification determined in step 4840 .

In another embodiment of the invention, the reporting device is provided with feedback (eg, visual and/or audio) responsive to the asset manager classifying the asset. For example, a green light may be emitted if the classification is successful and a red light may be emitted if the classification fails (and other asset characteristics are required).

In one embodiment of the invention, method 4800 includes populating a database with asset characteristics. For example, a database may be populated with reporting device identifiers and associated asset properties.

SECTION XIII: CONTROL OF POWER CONSUMPTION OF REPORTING DEVICES

Embodiments of the invention include a system and method for managing power consumption of reporting devices associated with assets. In particular, embodiments of the present invention relate to minimizing the power consumption of the reporting device, but still reporting the necessary information back to the asset manager.

Many times, the reporting device is coupled to an asset that does not have a power source or the asset is unable to provide power to the asset. In this case, the reporting device needs to be self-powered (eg, battery, solar, etc.). Often, the available power sources are limited and there is a need to conserve power. To help reduce power consumption, in one embodiment of the invention, the reporting device has an active mode and a sleep mode. In sleep mode, power consumption is much lower than in active mode.

While saving power is beneficial, it also requires the reporting device to work as intended and report various information back to the asset manager as designed. In order to balance power consumption and functionality, embodiments of the present invention provide a system and method for controlling power usage of reporting devices.

In one embodiment of the invention, the reporting device remains in sleep mode until a change in location of the asset is determined. In response to the change in location, the reporting device is powered on from the sleep mode to the active mode. In one embodiment of the invention, the reporting device transmits information back to the asset manager when powered on in active mode, including, for example, the previous location and the new location.

In another embodiment of the invention, the reporting device is periodically powered on from sleep mode to active mode to transmit information to the asset manager. In this case, the periodic power-on may be reset by a state change, such as an unexpected movement of the asset. In this embodiment. In addition to periodic reporting to the asset manager, the reporting device also reports status changes to the asset manager.

FIG. 49A is an illustration of an exemplary work site 4920A including a plurality of reporting devices with reduced power consumption according to embodiments of the present invention. It should be understood that worksite 4920A is for illustration purposes only and may be any area that includes traceable assets.

In one embodiment of the invention, work site 4920A includes a geofence 4950 . In FIG. 49A , geofence 4950 includes reporting devices 4971 , 4972A, and 4973 . It should be understood that the reporting devices are each coupled to an asset (not shown for clarity). Embodiments of the invention notify the asset manager when the asset changes state, eg, leaves the geofence 4950.

Referring to FIG. 49B , reporting device 4972B is outside geofence 4950 . Embodiments of the invention determine a state change (eg, movement) of reporting device 4972B and report the state change to an asset manager (not shown). In one embodiment of the invention, thresholds may be assigned to states where the asset is allowed to operate within a predetermined range of states without powering on and reporting state changes to the asset manager. For example, an asset could be allowed to move within a geofence without triggering a state change to power up. It should be understood that state changes are not limited to physical movement of assets. For example, a state change can be any measurable parameter, such as maintenance intervals, location, temperature, orientation, etc.

50 is a block diagram of an exemplary method 5000 for managing power in a reporting device according to an embodiment of the invention. In step 5002, method 5000 includes determining that the reporting device is in sleep mode or active mode. In one embodiment of the invention, when the reporting device is in sleep mode, less power is consumed than when the reporting device is in active mode.

In step 5004, method 5000 includes responding to determining that the device is in a sleep mode, step 5004 includes maintaining the sleep mode. In one embodiment of the present invention, the default power state is sleep mode to reduce the overall power consumption of the reporting device.

In step 5006, method 5000 includes responding to determining a state change associated with the reporting device, step 5006 includes powering on the reporting device to an active mode.

In step 5008, method 5000 includes reporting the status change to the asset manager. It should be appreciated that during step 5008, the reporting means may report information other than or other than a state change to the asset manager. It should also be appreciated that in response to reporting to the asset manager, the asset manager can transmit information back to the reporting device. In one embodiment of the invention, the communication between the reporting device and the asset manager is performed wirelessly.

In one embodiment of the invention, after reporting a state change in step 5008, the reporting device is powered off into sleep mode. In one embodiment of the invention, after reporting to the asset manager in step 5008, the reporting device remains in active mode for a predetermined period of time.

In one embodiment of the invention, the reporting device is periodically powered on as an active power state even if no state change is determined. Periodic power-ups provide a degree of assurance that the asset is being monitored, even if the asset has not changed state. If the reporting unit is unable to complete a power cycle, it can be assumed that there is a problem with the reporting unit or asset.

In one embodiment of the invention, the asset manager generates an alarm in response to receiving a state change of one or more assets. In another embodiment of the invention, the status-related thresholds are implemented at an asset manager level, where all status changes of the asset are reported to the asset manager and the asset manager determines whether an alarm should be generated.

51 is a flowchart of an exemplary method 5100 for powering on a reporting device in response to detecting movement of an asset, according to an embodiment of the invention.

In step 5102, method 5102 includes detecting movement of an asset from a first location to a second location. In one embodiment of the invention, the positioning movement is determined by GPS. However, it should be understood that any means for determining positioning may be used. For example, mercury changes can be used to determine movement. In one embodiment of the invention, step 5102 includes determining the distance moved. In this embodiment of the invention, a threshold can be used to determine if the distance triggers power-up and reporting to the asset manager.

If the reporting device associated with the asset is in sleep mode, step 5104 includes powering on the reporting device to active mode and reporting the movement to the asset manager.

If the reporting device is in active mode, step 5106 includes reporting the movement to the asset manager.

Step 5108 includes powering down the reporting device into a sleep mode in response to the reporting performed in step 5106.

Table 1 includes exemplary pseudocode for a method of reducing power consumption of a reporting device according to an embodiment of the present invention.

Table 1

52 is a block diagram of an exemplary system for reducing power consumption of reporting device 208 according to an embodiment of the invention. In one embodiment of the invention, the reporting device 208 includes a power manager 5110 . In one embodiment of the invention, power manager 5110 includes power state controller 5116 . The battery state manager 5116 determines the battery state of the reporting device and can power on the reporting device from sleep mode to active mode and can power off the reporting device from active mode to sleep mode.

Location determiner 5112 provides location information to state of charge controller 5116 . It should be appreciated that location determiner 5112 may be any device capable of determining the location or location of reporting device 208 . It should also be appreciated that location determiner 5112 may be part of power manager 5110 , part of reporting device 208 , or even external to reporting device 208 .

The reporting device 208 also includes a reporter 5114 . The reporter communicates with the asset manager 300 . In one embodiment of the invention, the asset manager generates an alert 5190 in response to receiving a report from the reporting device 208 .

Part XIV: Passing Custom Asset Information to Devices

overview

In general, the present technology provides a system and method for delivering asset signals to devices in a user-defined dashboard format customized for a specific device. The term dashboard refers to a visual display that provides information in a format similar to a vehicle dashboard. For example, in a vehicle, the driver can monitor speed, RPM, oil temperature and similar parameters. In the same way, project managers wish to monitor project metrics such as cost, asset usage, labor, security, diversity, environmental issues, and similar metrics.

Dashboards provide an exemplary means of presenting any or all desired project metrics in a quick-to-understand overview-type format. Furthermore, in one embodiment, when interacting with the dashboard, the user can select one of the metrics (eg, cost), which will then invoke a more detailed dashboard information view behind the cost metric. For example, cost metrics may include labor, materials, fines, delays, savings, and the like. In one embodiment, the depth of layers of the dashboard is limited only by the availability of asset data.

Basically, the present technology provides a data delivery system for presentation on the displays of computing devices, such as mobile phones, personal digital assistants, laptops, desktops, and the like. In one embodiment, data is collected by asset management system 300 from a database, such as database 205 of FIG. 3 , and includes status reports on aspects of projects or operations. In one embodiment, data transfer is via a direct link to a data collection server (eg, a direct contact line), via a network connection, via Internet-based virtual circuit access, or the like.

In one embodiment, the displayed results are predetermined or selected based on a user selectable field in the settings menu and can be easily adjusted for each assignment, each grade, each time period, and the like. Additionally, settings can be accessed from any internet access device and can be adjusted via drop down menus or customized by the customer. In one embodiment, a dashboard may be a hardwired view, eg, providing access to data via the device and allowing the device to format incoming data to create a dashboard view. However, the present technology is also well suited to allow devices to have the option to utilize a web page view instead of a hardwired view. Basically, web view means that the device's internal software does not require any formatting. Formatting accompanies downloading data from web access. So, by having the web view also be user formatted in a predefined way, the foreign 'content' no longer exists on the web view but only on the user defined display.

Referring now to FIG. 53A , shown is a block diagram of an exemplary handheld computing device 5305 in accordance with an embodiment of the present invention. In one embodiment, handheld computing device 5305 includes GUI 5310 and interaction buttons 5320 . Typically, handheld computing device 5305 is a device such as, but not limited to, a personal digital assistant (PDA), a mobile telephone, a pager, a hand-held portable computing device, and the like.

In one embodiment, the dimensions of the GUI 5310 of the handheld computing device 5305 are also known. In one embodiment, this dimension is provided as a diagonal measurement 5312. However, the inventive technique is well suited for providing GUI 5310 dimensions in other measurements, such as length, width, pixelation, dots per inch (DPI), and the like.

Referring now to FIG. 53B , shown is a block diagram of an exemplary computer system 5345 in accordance with one embodiment of the present invention. In one embodiment, computer system 5345 includes GUI 5360 and keyboard/thumbpad 5380. In one embodiment, the computer system 5345 is a device such as a laptop computer that can be held by a user. In one embodiment, the computer system 5345 is a stationary computing device, such as a desktop system, vehicle mounted system, in-dash computing system, network television system, server terminal system, or any other type of computing device that includes a GUI 5360.

In one embodiment, the dimensions of the GUI 5360 of the computer system 5345 are also known. In one embodiment, the dimensions are provided in the form of diagonal measurements 5352. However, the inventive technique is well suited for providing GUI 5360 dimensions in other measurements, such as length, width, pixelation, DPI, and the like.

Referring now to FIG. 54A , there is shown a block diagram of an exemplary list 5400 of top-level item-related user-selectable options 5410 for defining a GUI dashboard, in accordance with one embodiment of the present invention. In one embodiment, the project-related user selectable options 5410 include schedule 5422 , cost 5424 , labor 5426 , and equipment 5428 . In one embodiment, schedule 5422 refers to projects being on schedule or projects ahead or behind schedule. Cost 5424 refers to the item at the original price, lower than the original price or more than the original price. Labor 5426 refers to the percentage of manpower assigned and paid for on the project. Equipment 5428 refers to the percentage of machinery assigned and paid for on this project.

Although a number of items are provided here regarding user selectable options 5410, they are exemplary. That is, the inventive technique is well suited for user selectable options 5410 with more and fewer items. Furthermore, the inventive technique is well suited for item-related user-selectable options 5410 other than those presented herein. The use of user selectable options 5410 in terms of items provided here is for brevity purposes only.

Additionally, item-related user selectable options 5410 may be provided or limited based on the size of the GUI that is about to present the information. For example, a user may begin defining a dashboard for a handheld device, such as device 5305 of FIG. 53A. In this way, the user can input the device to receive information. For example, a user may choose a mobile phone with a standard display, a PDA with a 4 inch GUI, or similar. As such, item-related user-selectable options 5410 may be modified depending on the display screen.

In another embodiment, the list of item-related user-selectable options 5410 may not be modified based on GUI size, but the number of options allowed may be limited. For example, a user building a dashboard for a mobile phone might only be able to select two of four item-related user-selectable options 5410.

In general, item-related user selectable items 5410 refer to any item related to the information that the user wants to receive. In other words, as described in more detail herein, there may be multiple items and any or all of the items may have item-related user selectable options 5410 available. Thus, a user may choose to receive information about one item, all items, or any combination thereof. Additionally, for each selected item, the user may choose to receive similar information or different information.

Referring now to FIG. 54B , there is shown a block diagram of an exemplary list of secondary user selectable options 5460 for defining a GUI dashboard, according to one embodiment of the present invention. In one embodiment, option level II 5460 is based on the initial selection of equipment 5428. While option level II 5460 is focused on device 5428, this is exemplary. That is, the inventive technique is well suited for providing a second level of information based on any or all of the item-related user-selectable options 5410 .

In one embodiment, device 5428 has multiple sub-levels, including asset 5465, location 5470, and status 5475. In one embodiment, asset 5465 refers to the type of asset, exact asset, basic profile of similar assets, or the like, location 5470 refers to the location of the asset and status 5475 refers to the status of the asset, e.g., operational, damaged, Maintenance and stuff like that should be done.

Although multiple secondary levels are provided here, they are exemplary. That is, the inventive technique is well suited for more and fewer secondary. Furthermore, the inventive technique is well suited for sub-levels other than those presented herein. The secondary usage is provided here for the purpose of brevity only.

Additionally, the number of secondary options may be provided or limited based on the size of the GUI on which the information is to be displayed. For example, a user may begin defining a dashboard for a handheld device, see device 5305 of FIG. 53A. In this way, the user may enter the device as part of the user input. For example, a user may submit that the dashboard outline will be based on a mobile phone with a standard display, a PDA with a 4 inch GUI, or similar device. As such, the second level options for device 5460 may be modified depending on the display.

In another embodiment, the list of second-level options for device 5460 may not be modified, but the number of allowed options may be limited. For example, a user building a dashboard about a mobile phone might only be able to select two of four second-level options about the device 5460.

Referring now to FIG. 55A , shown is a block diagram of an exemplary top-level user-defined GUI dashboard 5500 in accordance with one embodiment of the present invention. In one embodiment, the GUI dashboard 5500 includes a first item 5420A and a second item 5420B. Additionally, at GUI dashboard 5500, the user has chosen to monitor plans 5422, costs 5424, labor 5426, and equipment 5428 for various projects. Although, in one embodiment, the options for each item are the same, the techniques of the present invention are well suited for monitoring different aspects of each item. That is, descriptions about the same options for each item are provided here for the sake of brevity only.

In one embodiment, the number of items displayed on the GUI dashboard 5500 can be selected by the user and is limited by the current GUI size. Additionally, if more than two items are selected, the inventive technique may allow the user to select the order of the items to be displayed and then the items may be rotated based on the order of the user's selection. For example, if five items are selected for monitoring and the GUI can only display two at a time, then the items can be rotated across the screen automatically, or when prompted, in a user-defined order. In another embodiment, other items may be accessed via scroll bars, hotkeys, or the like.

Referring now to FIG. 55B, shown is a block diagram of an exemplary second-level user-defined GUI dashboard, according to one embodiment of the present invention. In one embodiment, the second level user-defined GUI dashboard 5500 provides information about items 5420A to devices 5428A. Additionally, at the second level user-defined GUI dashboard 5550, the user has selected to monitor assets 5465, location 5470 and status 5475 with respect to equipment 5428.

In one embodiment, the number of device sub-options displayed on the second level user-defined GUI dashboard 5550 can be selected by the user and is limited by the current GUI size. In addition, if more than three sub-options bars are selected, the present technology may allow the user to select the order of the sub-options to be displayed and then may rotate the sub-options based on the user's selection order. For example, if five suboptions are selected to monitor and the GUI can only display three at a time, then the suboptions can be rotated through the screen automatically or when prompted, in a user-defined order. In another embodiment, other sub-options may be accessed via scroll bars, hotkeys, or the like.

Referring now to FIG. 56 , there is shown a flowchart 5600 of an exemplary method for communicating custom asset information to a device in accordance with one embodiment of the present invention. As described herein, the present technology allows a user to customize asset information received for a device based on GUI properties or other characteristics of the device. For example, a user receiving asset information on a 17" display may customize asset information in a first layout, and when a user intends to receive asset information in a 3" display, the user may customize asset information in a second layout. In one embodiment, the first and second layouts may differ in the amount of information provided in the asset information. In another embodiment, the first and second layouts may differ in presentation methods. In yet another embodiment, the first and second layouts may differ in both the amount of asset information provided and the method by which the asset information is presented.

Referring now to 5602 of FIG. 56 and FIG. 3 , one embodiment accesses database 205 that includes information about assets from a first reporting source and information about assets from a second reporting source. Additional details of database 205 are depicted in reference to FIG. 3 and are not provided here for brevity.

Referring now to 5604 of FIG. 56 and FIG. 54A , one embodiment utilizes predefined user-selectable criteria 5400 to select asset information from a first reporting source and a portion of information from a second reporting source. For example, once user-selectable criteria 5400 have been defined, only information selected by the user will be provided when accessing asset management system 300 of FIG. 3 . Additional details of the operation of the asset management system 300 have been provided above and are not presented here for the sake of brevity.

Referring now to 5606 of FIG. 56 and FIGS. 55A and 55B , one embodiment includes customizing asset information reports 5500 , wherein a predefined portion of information about assets is used in customizing asset information reports 5500 . For example, in one embodiment, custom asset information report 5500 may include formatting a first level of detail for custom asset information report 5500 . Additionally, a user may also predefine a second level of detail for formatting a custom asset information report 5500 . In other words, the first level of detail may be an overview, such as that shown in GUI 5500 of FIG. 55A, and the second level of detail may be a drill-down of a specified portion of the first level of detail as shown in GUI 5550 of FIG. 55B. .

Additionally, a second level of detail can be defined and used for any or all of the information within the first level of detail profile. For example, a user can monitor a first level of detail, e.g., GUI 5500, and then can select one of the overview sections, e.g., device 5428A of FIG. 55B, to view in more detail.

Referring now to 5608 of FIG. 56 and FIGS. 55A and 55B, one embodiment constructs the layout of the custom asset information report 5500 based on a GUI, such as GUI 5310 of FIG. 53A. In one embodiment, the layout of the custom asset information report 5500 is constructed based on the display dimensions of the GUI 5310. Additionally, a job identifier is assigned to the construction of the custom asset information report 5500 .

For example, the president of a company wants to see predefined versions of any or all projects involving the company. In one embodiment, the president of the company will select the format of the pre-defined version using a method (eg, a user selectable field in a settings menu), working with a technician, or the like. For example, a predefined version may be a high-level overview of any or all projects and may include project name, project status, project actual cost and budget, or the like.

In addition, the president of the company can establish multiple predefined versions based on differences in the GUIs that are planned to be viewed. For example, when accessing information on a portable computing system such as laptop computer 53B, the first predefined version may include a large number or even all items related to the company. However, when accessing information from a handheld device 53A, such as a mobile phone, personal digital assistant, or other small screen size device, the second predefined version may provide the items in a certain rotational order, utilizing scrolling type functionality, and monitoring a smaller number of items , reducing the variables displayed per item and similar. In this way, the user will receive the required predefined information in an easy to read and navigate format based on user defined preferences and the GUI characteristics of the device receiving the information.

In a different embodiment, a project manager wishes to view, e.g., on a GUI 5310 or similar device, predefined versions of any or all projects involving the administrator. In one embodiment, the project manager will establish the pre-defined version through some method (such as a user-selectable field in a setup menu), working with a technician, or similar. For example, a predefined version could be a high-level profile of any or all items that concern the administrator. Predefined versions may include project name, project status, project actual cost and budget, or similar. In one embodiment, a project manager can create multiple predefined versions in a similar manner as described herein based on differences in the GUI or devices that are planned to be viewed.

In addition, project managers can create predefined drilldown versions of multiple asset reports. For example, a project manager may have an initial predefined version that provides project name, status, and labor. The project manager can then create predefined versions of each of the original fields such that selection of one of the fields (eg, manpower) provides a predefined version of any or all data related to manpower. For example, number of casualties, safety records, people on the job, people off the job, or similar.

In one embodiment, the number of user-defined levels is limited only by the data in the database and the user's needs. For example, a company president can pre-define drilling characteristics ranging from an overview of a project to a maintenance schedule for a specific truck. In this way, the predefined asset management versions not only start to provide an overview of the entire company project when accessed, but also allow the user to explore any predefined details.

Furthermore, because asset management information is predefined, if a particular aspect of a particular project becomes a concern, the company president can redefine the initial top-level GUI asset monitoring information to include details about that particular aspect of that particular project without requiring User exploration. That is, the user is able to define what information is displayed at what level on each utilized display and what details are provided within that information. Conveniently, this is accomplished without requiring the user to navigate through unnecessary data, find redundant reports, navigate using undersized displays, and the like.

In one embodiment, when the layout of the custom asset information report 5500 is larger than the display size of the GUI 5310, a user-selectable rotation order can be defined for the layout of the asset information within the report. For example, the first portion of the layout of the custom asset information report 5500 is initially displayed on the GUI 5310. Then, after a period of time based on user input or any other criteria, the first portion of the layout of the customized asset information report 5500 will be removed and then a second portion of the layout of the customized asset information report 5500 will be displayed on the GUI 5310. This page rotation can last for any number of layout pages. Additionally, the rotation can be reversed, dragged, hotkeyed, or the like to allow the user to define the order in which pages are viewed, to modify the order in which pages are viewed, or to jump from one page to another specified regardless of any pre-assigned page order.

In another embodiment, a layout navigator is provided as part of the layout of the customized asset information report 5500 when the layout of the customized asset information report 5500 is larger than the display size of the GUI 5310. For example, a layout navigator may be a scroll bar, a set of scroll bars, an arrow, or any other type of receivable input that allows a user to navigate a larger file layout using a window smaller than the size of the file layout being presented. In other words, if a layout has a visual size of 10" x 10" and a screen size of 5", only a portion of said layout can be generated on the GUI at any given time. However, utilization of the layout navigator allows the user to modify What part of the layout of the custom asset information report 5500 is visible on the GUI 5310. That is, the user can use the layout navigator to navigate within a visual size of 10" x 10" when the screen size is 5".

In addition to allowing the user to construct a first layout of the custom asset information report 5500 based on a first display size of the GUI, the present technology also allows the user to construct a second layout of the custom asset information report 5550 with at least one level of detail based on a second display size of the GUI. layout. For example, a user may construct a first custom asset information report 5500 based on a first device, such as the laptop computer 5345 of FIG. The PDA 5305 of FIG. 53A of FIG. 5312 constructs a second custom asset information report 5550. Additionally, the user may assign a first job identifier to the first layout configuration and a second job identifier to the second custom asset information report 5550. Layout Construction. Thus, when a user is ready to access information, the user can enter a job identifier to receive a report structured for the device being utilized.

For example, if the user is utilizing a laptop computer, the user may access the Internet or another network to establish a connection with an asset management system that provides asset reports. If required, the user can log in and provide a password to establish their identity with the asset management system. The user can then enter a first job identifier. The asset management system can then provide a predefined layout built for a 17" GUI. In one embodiment, the first layout can include many details due to the amount of space available to display information. However, if the user is utilizing a mobile device, then The user can enter a second job identifier and the received layout can be configured for a 5" display. Thus, in one embodiment, the second layout may not include as much detail as the first layout, may monitor fewer aspects than the first layout, may require the user to navigate through the layout, may need to scroll through a large number of pages, or similar practice. In other words, the user may specify a second layout to reduce the information, or may specify a method by which the information remains the same and designed for navigating back and forth within the layout.

Embodiments of the system and method of the present invention for asset management are thus described. While the invention has been described in particular embodiments, it should be understood that the invention should not be construed as limited to these embodiments, but rather constructed in accordance with the following claims.

Section XV: Microfluidic Analysis of Telematics Assets

Notes and Naming

Unless expressly stated otherwise in the following discussion, it should be understood that throughout the description of the embodiments of the present invention, references to terms such as "obtain", "analyze", "display", "provide", "start", "transmit", "compare" ” or terms of similar terms refer to the actions and processes of a computer system or similar electronic computing device (or a portion thereof), such as, but not limited to, an electronic control module, a telematics device, and/or a management system (or a portion thereof ). An electronic computing device manipulates and transforms data represented as physical (electronic) quantities within the processors, registers and/or memory of an electronic computing device into Other data similarly represented as physical quantities within other such information storage, processing, transmission and/or display components of the device.

Discussion overview

Example techniques, devices, systems, and methods for analyzing on-site fluids and providing analysis results to a remote management system are described herein. The discussion begins with high-level profiling of fluid analyzers and high-level profiling of telematics devices. An example fluid analysis system coupled to assets and telematics devices is then described. The discussion continues with a description of an example fluid analysis system. The components of the fluid analysis system are described subsequently. The discussion continues with a description of telematics devices and asset management systems. The components of the asset management system are then described. Operation of the fluid analysis system is then further described in conjunction with a description of an example method of analyzing the fluid and providing the results to the asset management system via the telematics device.

Fluid Analyzer

Fluid analyzers provide results related to fluid properties based on a set of parameters. Fluid analysis can be performed during routine maintenance to provide information about the condition of the fluid. By tracking sample results throughout a machine's life, the Fluid Analyzer assists tribologists by establishing trends, which can help eliminate costly repairs. The Fluid Analyzer can analyze fluid properties, including fluid additions. They can determine the presence and extent of fluid contamination and particulates. Fluid analyzers can also determine the type of particles found in a fluid sample. Additionally, fluid analyzers can determine the presence of wear debris from machinery.

Fluid sampling is the procedure of collecting a volume of fluid from an asset for analytical purposes. It is important that the procedures used to collect and test samples minimize sample disturbances during and after the sampling process. Conveniently, the sample is sent to a laboratory for analysis.

A lab-on-a-chip ("LOC") device to eliminate the time spent delivering fluid samples to the lab. The LOC can analyze extremely small fluid volumes down to less than a picoliter immediately. Microfluidic analyzers offer many advantages specific to their application. These advantages include, but are not limited to: low fluid volumes required to consume; faster analysis and response times due to short diffusion distances, rapid heating, high surface-to-volume ratio, and small heat capacity; faster system response times due to faster Optimal process control; compactness of the system; parallelization due to compactness, allowing high-throughput analysis; low manufacturing costs, allowing cost-effective disposable chips to be produced in mass production; and A safer test platform.

telematics device

Telematics refers to the integrated use of telecommunications and informatics. Telematics devices transmit data from an original location to a calculated location, and can exercise some degree of control over distant objects. Telematics refers to, for example, technologies that send, receive, and store information through telecommunication devices, combined to control distant objects; integrate telecommunications and informatics for vehicle applications; or global positioning system technologies.

Example Assets Coupled with Electronic Control Module, Fluid Analysis Control Module and Telematics Device

57 is a diagram of an example of an asset 5700 coupled with an electronic control module 5730 , a fluid analysis control module 5710 , and a telematics device 5720 . Fluid analysis control module 5710 receives a fluid sample from asset 5700 . Microfluidic analysis may occur in fluid analysis control module 5710, eg, via one or more LOCs included within or coupled to fluid analysis control module 5710. After analysis, the fluid analysis control module 5710 sends the results of the analysis to the telematics device 5720 .

In one embodiment, electronic control module 5730 , fluid analysis control module 5710 and telematics device 5720 are physically connected to asset 5700 . In this embodiment, the fleet manager can monitor the fluids in the fleet assets during deployment without dispatching technicians to the location of the assets 5700 to sample the fluids and without sending the sampled fluids to a lab and waiting for the results back . In one embodiment, the majority of the electronic control module 5730 is comprised of a J1939 vehicle bus or other similar vehicle bus architecture (also referred to as "J-Bus").

In another embodiment, electronic control module 5730 , fluid analysis control module 5710 and telematics device 5720 are not attached to asset 5700 . For example, one or more of electronic control module 5730 , fluid analysis control module 5710 , and telematics device 5720 may be housed in a handheld device that a technician may insert into a fluid sample source of asset 5700 . In various embodiments, the electronic control module 5730, fluid analysis control module 5710, and telematics device 5720 may be housed together in one unit, or the electronic control module 5730, fluid analysis control module 5710, and telematics device 5720 may be separate from each other.

In some embodiments, asset 5700 is a type of heavy machinery that may typically be used in construction. Heavy machinery includes, but is not limited to: backhoes, truck lifts, cold planers, compactors, conveyors, cranes, curing rigs, bulldozers, excavators, dump trucks, backhoes, loggers Stackers, Forklifts, Conveyors, Sorters, Harvesters, Handlers, Haulers, Loaders, Pavers, Pile Drivers, Pipelayers, Recyclers, Rollers, Buckets, Skidders, Soil Stabilization machines, road clearers, tillers, tractors, trenchers, trucks, roadheaders and log stackers. In other embodiments, asset 5700 may be, for example, a customer automobile, vessel, appliance, or heavy tool that could benefit from fluid analysis.

In other embodiments, asset 5700 is a class of vehicles including, but not limited to: airplanes, customer trucks and cars, spacecraft, and ships. In other embodiments, assets 5700 are non-vehicles, including but not limited to: exoskeletons, habitats, platforms, wind turbines, or greenhouses.

Example telematics asset microfluidic analysis system

58 is a block diagram of an example of a telematics asset microfluidic analysis system. According to one embodiment, fluid analysis control module 5710 is coupled to telematics device 5720 that provides analysis results to asset management system 5800 . FIG. 58 also illustrates components that may include a fluid analysis control module 5710. In one embodiment, the fluidic analysis control module 5710 includes a microfluidic analyzer 5811 , an analysis controller 5812 , a results compiler 5813 and a fluidic results analyzer 5816 .

In one embodiment, microfluidic analyzer 5811 receives fluid sample 5825 from fluid sample input 5820 . Fluid sample input 5820 may be fluidly coupled to fluid source 5815 of asset 5700 and operative to obtain fluid samples 5825 on demand. Fluid sources 5815 may include, but are not limited to: oil filters, oil reservoirs, oil fluid lines, hydraulic fluid reservoirs, hydraulic fluid lines, drilling fluid lines, brake fluid reservoirs, brake fluid lines, transmission fluid Reservoirs, torque converter reservoirs, fluid reservoirs for clutch hydraulics, coolant reservoirs, coolant fluid lines, antifreeze reservoirs, antifreeze fluid lines, transmission fluid reservoirs , transaxle fluid reservoir, power steering fluid reservoir, power steering fluid line, battery, windshield wiper fluid reservoir, windshield wiper fluid line, and fluid filter. In some embodiments, the microfluidic analyzer 5811 circulates the sample 5825 back into the fluid source 5815 through a fluid sample output 5830 fluidly connected to the fluid source 5815 . In other embodiments, the microfluidic analyzer 5811 discards the fluid sample 5825 without returning the fluid sample to the fluid sample source 5815 via the fluid sample output 5830 . For example, excess sample not completely used up in the analysis may be stored by fluid sample output 5830 for subsequent disposal according to the concentration contained in the environment.

The fluid analysis control module 5710 also includes an analysis controller 5812 that initiates collection of a fluid sample 5825 via a fluid sample input 5820 and also initiates microfluidic analysis of the sample 5825 . Analysis controller 5812 responds to the occurrence of an analysis trigger condition. Analysis triggers may be internal triggers within fluid analysis control module 5710 and/or asset 5700, or may be externally received triggers. Analysis trigger conditions (internal trigger conditions) may include operational characteristics of asset 5700 coupled to fluid analysis control module 5710 . Some examples of such internal analysis triggers include, but are not limited to: elapsed operating time of the Asset 5700, operating temperature of the Asset 5700, ambient temperature in which the Asset 5700 is operated, exceeding a predetermined revolutions per minute (RPM) level in the engine , exceeded predetermined torque level in transmission, exceeded predetermined time from last sample, current time, asset 5700 energized, asset 5700 deenergized, oil temperature, oil pressure, hydraulic fluid pressure, hydraulic fluid temperature, power steering Fluid pressure and brake fluid pressure. Additionally, the fluid analysis control module 5710 may include instructions to trigger analysis when a particular combination of operating characteristics occurs. For example, according to one embodiment, the combination may be that the engine RPM exceeds a threshold (e.g., 4000 RPM) for a specified time (e.g., two minutes) while the asset is on, while the engine and/or ambient temperature is below a certain threshold (e.g., -20 degrees Fahrenheit). An example of an external trigger is instructions received via telematics device 5720 where the instructions received direct fluid analysis control module 5710 to sample and analyze a particular fluid of asset 5700 .

The fluid analysis control module 5710 also includes a fluid results analyzer 5816 . Fluid Results Analyzer 5816 receives results from Results Compiler 5813 . Once the results are received, fluid results analyzer 5816 provides the data to analysis controller 5812, telematics device 5720, or both. In some embodiments, the output of the results analysis performed by the fluid results analyzer 5816 may include triggers that cause the analysis controller 5812 to direct other microfluidic analyzes to be performed by the microfluidic analyzer 5811. For example, in one embodiment, if the results of a microfluidic analysis of engine oil are reviewed by fluid results analyzer 5816 and it is determined that the viscosity of the oil is below an established threshold, then this may trigger the implementation of a method for targeting metal particles in engine oil. secondary microfluidic analysis.

In some embodiments, the analysis controller 5812 is configured to initiate a first type of analysis of a sample in response to a first analysis trigger condition, and to initiate a second, different type of analysis of the same sample in response to the occurrence of a second analysis trigger condition. In some embodiments, more than two analyzes may be performed in response to various trigger conditions. That is, in some embodiments, the number of analyzes initiated by the analysis controller 5812 is not limited to two, but may be three, four, or more, depending on the number and type of analysis triggers experienced and reside in Depending on the microfluidic analysis capability in the fluid analysis control module 5710. In some embodiments, the analysis controller 5812 can be configured to begin collecting a second sample for the second type of analysis without analyzing the same sample using two different types of analysis. For example, if the RPM level in the asset 5700 exceeds a certain level; then the analysis controller 5812 can be triggered to start an oil analysis that analyzes oil for molecular fragmentation and another analysis that analyzes oil particles. In another example, the analysis controller 5812 may analyze the viscosity of the oil if the temperature of the oil drops below a certain ambient temperature. In another example, the analysis controller 5812 may be triggered and begin a transmission fluid analysis if the torque level in the transmission exceeds a certain level.

After the microfluidic analyzer 5811 has completed an analysis, it provides the results of the analysis to the results compiler 5813 . Results compiler 5813 is also included in fluid analysis control module 5710. In some embodiments, the microfluidic analyzer 5811 can perform various analyzes and the results compiler 5813 will store and compile the results of the analyzes and then provide the results to the fluidic results analyzer 5816.

In some embodiments, media source 5814 adds media to fluid analyzer 5811 to facilitate certain types of tests. This medium could be some type of fluid that needs to be tested, or another type of object. The medium can be in a refillable container or can be recycled after each test is completed. In some embodiments, the media source 5814 is external to the fluid analysis control module 5710 .

In some embodiments, fluid samples 5825 may include, but are not limited to, fluids such as: oil, hydraulic fluid, drilling fluid, antifreeze, coolant, transmission fluid, torque converter fluid, clutch hydraulic fluid, drive Axle fluid, transmission fluid, brake fluid, power steering fluid, battery acid and windshield wiper fluid.

Telematics device providing results to asset management system

FIG. 58 also shows telematics device 5720 coupled to fluid analysis control module 5710 . In certain embodiments, fluid results analyzer 5816 provides analysis results to telematics device 5720 . After the telematics device 5720 receives the analysis results, the telematics device 5720 wirelessly transmits the analysis results to the asset management system 5800 . It should be appreciated that in some embodiments, analysis results and/or other information received from the telematics device 5720 may be stored in a storage system and/or database of the asset management system 5800, and that the asset management system 5800 may receive data from the telematics device 5720 Or receive other information about asset 5700 (and other assets) from other reporting sources (as already described herein). As one non-limiting example, another reporting source coupled to or independent of asset 5700 may provide the location of asset 5700 to asset management system independently of any information provided to asset management system 5700 by telematics device 5720 .

In certain embodiments, the telematics device 5720 provides the results to at least one asset management system 5800 via radio, microwave, or optical wireless communication means. In certain embodiments, telematics device 5720 may provide results via a point-to-point link, a broadcast link, or a multipoint link.

In certain embodiments, the asset management system 5800 includes a results analyzer 5801 . The result analyzer 5801 converts the analysis results into various actions. For example, result analyzer 5801 may include a lookup table that associates particular results with particular actions.

Figure 59 illustrates an example of an asset management system 5800 providing fluid analysis results, according to an embodiment. For example, results analyzer 5801 may instruct asset management system 5800 to send alerts to individual employees, providing results to various receiving devices 5900 (asset installable/detachable devices 5910, portable computing devices 5920, smartphones 5930, personal digital Assistants 5940, mobile phones 5950, global navigation satellite system (GNSS) survey vehicles 5960, human users 5970 (such as via audio notifications) and machine control systems 5980) or remotely power off assets 5700 that are at risk of damage.

In certain embodiments, results analyzer 5801 may instruct asset management system 5800 to provide results to various receiving devices 5900 . For example, asset management system 5800 can: send alerts to cellular devices including smartphones and personal digital assistants; send alerts via email to a construction manager's laptop; or send commands directly to asset 5700. In certain embodiments, results analyzer 5801 may utilize information received from telematics device 5720 and from one or more additional reporting sources in determining an action, such as an alert or notification. For example, if the fluid analysis results received from the telematics device 5720 indicate that the asset 5700 needs maintenance, the location of the asset 5700 received from the secondary reporting source may be used by the results analyzer 5801 to select the mechanic closest to the asset 5700 (e.g. , from the list of approved mechanics) to send maintenance dispatch orders.

In some embodiments, the asset management system 5800 can provide the results to a graphical user interface. In other embodiments, the results may cause the receiving device to modify the behavior or operating characteristics of the asset 5700. For example, electronic control module 5730 may limit engine RPM, shut down asset 5700, or lock asset 5700 from (e.g., prevent starting or using) a or multiple modes of operation. For example, the asset management system may telematically direct electronic control module 5730 (or other telematically coupled device located on/associated with asset 5700 ) to limit the engine RPM of asset 5700 in response to analysis results indicative of motor oil viscosity breakdown.

Example computer system environment

Referring now to FIG. 1 , all or a portion of certain embodiments described herein consist of computer readable and computer executable instructions residing, for example, in a computer usable/computer readable storage medium of a computer system. That is, FIG. 1 illustrates one example of a type of computer (computer system 100 ) that may be used in accordance with, or may be used to implement, various embodiments discussed herein. It should be appreciated that the computer system 100 of FIG. 1 is merely an example and that implementations as described herein may be implemented on a variety of different computer systems, including but not limited to general purpose computer systems, networked computer systems, embedded computer systems, routers, switches, server devices , client devices, various intermediary devices/nodes, stand-alone computer systems, media centers, handheld computer systems, multimedia devices and the like) or within. The computer system 100 of FIG. 1 is well suited for utilizing local/peripheral tangible computer-readable storage media, such as, for example, RAM 104, ROM 106, and/or storage 118 (which may be, inter alia, or with direct access storage, floppy disks, optical storage disks) , Universal Serial Bus "U" disk, removable memory card).

Example how-to

Referring to Figures 60A-60D, a flowchart 6000 illustrates an exemplary procedure used by various embodiments. Flowchart 6000 includes processes and operations that, in various embodiments, are carried out by one or more of the devices shown in FIG. 58 or via computer system 100 or components thereof.

Although specific procedures are disclosed in flowchart 6000, these procedures are examples. That is, the implementation is well suited for performing various other operations or variations of the operations set forth in the process of flowchart 6000 . Also, in some embodiments, the operations in flowchart 6000 may be performed in an order different from that presented, not all operations described in one or more of these flowcharts may be performed, and/or one or more of the operations described in these flowcharts may be added. Multiple additional operations.

The operations of certain exemplary methods of operation of the proposed embodiments are discussed below in detail. Referring to Figures 60A-60D, a flowchart 6000 illustrates an exemplary procedure used by various embodiments. Flowchart 6000 includes certain procedures that, in various embodiments, are carried out by a processor under the control of computer readable and computer executable instructions. In this manner, in various embodiments, the procedures described herein in connection with flowchart 6000 are implemented or can be implemented using a computer. Computer-readable and computer-executable instructions may reside in any tangible computer-readable storage medium, such as, for example, in data storage features (of FIG. 1 ) such as RAM 104, ROM 106, and/or storage 118. Computer readable and computer executable instructions residing on a tangible computer readable storage medium are designed to control or operate in conjunction with, for example, one or some combination of processor 102 or other similar processors. Although specific procedures are disclosed in flowchart 6000, these procedures are examples. That is, the embodiment is well suited for implementing various other procedures set forth in flowchart 6000, or variations of the procedures described. Also, in some embodiments, the procedures in flowchart 400 may be performed in an order different from that presented and/or not all of the procedures described in one or more of Figures 60A-60D may be performed. It should also be appreciated that one or more of the procedures described in flowchart 6000 may be implemented in hardware, or a combination of hardware and firmware, or a combination of hardware and software running on hardware.

60A is a flowchart 6000 of an exemplary method of analyzing a fluid, according to an embodiment. Reference will be made to the elements of FIGS. 57 and 58 to facilitate explanation of the method operations of flowchart 6000 . In one embodiment, the method of flowchart 6000 describes the use of microfluidic analyzer 5811 in analyzing fluid sampled from sample fluid input 5820 .

At operation 6010, in one embodiment, the fluid analysis control module 5710 samples asset fluid in response to the occurrence of an analysis trigger condition. Analysis controller 5812 detects analysis trigger conditions and begins sample acquisition and microfluidic analysis. For example, an analysis trigger may be an event including, but not limited to: elapsed operating time, operating temperature of the asset, ambient temperature in which the asset is being operated, exceeding a predetermined RPM level of the engine, exceeding a predetermined torque level while in transmission, exceeding a predetermined RPM level from the last Scheduled time for sample start, current time, asset powered on, asset powered off, oil temperature, oil pressure, hydraulic fluid pressure, hydraulic fluid temperature, power steering fluid pressure, and brake fluid pressure.

At operation 6020 , in one embodiment, the microfluidic analyzer 5811 analyzes the sample in response to an analysis trigger detected by the analysis controller 5812 .

At operation 6030 , in one embodiment, the microfluidic analyzer 5811 provides analysis results to the telematics device 5720 .

At operation 6040 , in one embodiment, the flowchart 6000 also includes an agent source 5814 that can provide a test agent to the microfluidic analyzer 5811 . For example, microfluidic analyzer 5811 will collect an oil sample via fluid sample input 5820 . The reagent source 5814 will then provide the microfluidic analyzer 5811 with specially formulated chemicals to facilitate a particular type of test within the microfluidic analyzer 5811.

At operation 6050, in one embodiment, flowchart 6000 further includes performing a first type of analysis of the sample in response to occurrence of a first analysis trigger condition. The trigger condition is detected by the analysis controller 5812 starting the microfluidic analyzer 5811. A second type of analysis of the sample then occurs in response to a second different analysis trigger condition. The analysis controller 5812 also detects a second trigger condition.

In one embodiment, the method of flowchart 6000 further includes wirelessly transmitting from the telematics device 5720 the results received from the fluid analysis control module 5710 . In one embodiment, the results are communicated to the asset management system 5800.

At operation 6060 , in one embodiment, the telematics device 5720 transmits the results of the fluid analysis to the asset management system 5800 . For example, transmission of results may occur via radio, microwave or optical transmission.

At operation 6070 , in one embodiment, the result analyzer 5801 automatically compares the received result to the result response rules maintained by the asset management system 5800 . For example, an outcome analyzer may look for an outcome response rule and cause the asset management system 5800 to initiate a response.

At operation 6080, in one embodiment, the asset management system 5800 initiates the response specified by the response rule. For example, responses may include, but are not limited to: displaying analytical information on a graphical user interface to an asset owner at a remote location; displaying analytical information to an asset operator on a graphical user interface; powering off the asset; powering on the asset; and display analysis information on a PDA, cellular device or other receiver.

Section XVI: Telematics Microfluidic Analysis Using a Handheld Device

Notes and Naming

As will be apparent from the following discussion, unless expressly stated otherwise, it should be understood that throughout the description of embodiments of the present invention, references such as "obtain", "analyze", "receive", "display", "provide", "start ", "transmitting", "comparing" or similar terms refer to the actions and processes of a computer system or similar electronic computing device (or a portion thereof), such as, but not limited to, electronic control modules, telematics devices, and/or or management system (or part thereof). An electronic computing device manipulates and transforms data represented as physical (electronic) quantities within the processors, registers and/or storage of the electronic computing device into Other data similarly represented as physical quantities within other such information storage, processing, transmission, and/or display components of an electronic computing device.

Discussion overview

Exemplary techniques, devices, systems, and methods for analyzing on-site fluids and providing analysis results to a remote management system are described herein. The discussion begins with a high-level description of the fluid analyzer, a high-level description of the telematics device, and a high-level description of the handheld device. An exemplary fluid analysis system coupled to a telematics device is then described. The discussion continues with a description of an exemplary fluid analysis system. Then, the components of the fluid analysis system are described. The discussion continues with a description of the telematics device and management system. Then, describe the components of the management system. Operation of the fluid analysis system is then further described in conjunction with a description of an exemplary method of analyzing the fluid and providing the results to the management system via the telematics device.

Fluid Analyzer

Fluid analyzers provide results related to fluid properties based on a set of parameters. Fluid analysis may be performed to provide fluid condition information. By tracking sample results over time, the Fluid Analyzer assists tribologists by establishing specific fluid trends. The Fluid Analyzer analyzes fluid properties, including fluid additions. Fluid analyzers determine the presence and extent of fluid contaminants and particles. Fluid analyzers can also determine the types of particles found in a fluid sample. Additionally, the fluid analyzer can determine the presence of wear debris from the machinery.

Fluid sampling is the procedure of collecting a volume of fluid for analysis. In certain embodiments, the procedures used to collect and test samples minimize sample disturbance during and after the sampling process.

A lab-on-a-chip ("LOC") device to eliminate the time spent delivering fluid samples to the lab. Although commonly referred to as "microfluidic analyzers," LOCs can analyze extremely small fluid volumes down to less than a picoliter in many cases. Microfluidic analyzers offer many analytical advantages that are often specific to their application. These analytical advantages include, but are not limited to: low fluid volumes required; faster analysis and response times due to short diffusion distances, rapid heating, high surface-to-volume ratio, and small heat capacity; faster system response times Excellent process control; compactness of the system; parallelization due to compactness, allowing high-throughput analysis; low manufacturing cost, allowing cost-effective disposable chips for mass production; and safer testing due to smaller fluid volumes platform.

telematics device

Telematics refers to the integrated use of telecommunications and informatics. Telematics devices transmit data from an original location to a calculated location and can exert a degree of control over distant targets. Telematics may refer to, for example, the sending, receiving, and storing of information via telecommunications devices in conjunction with the control of distant objects; the integration of telecommunications and informatics for vehicle applications; and/or global positioning system technology.

Telematics refers to the integrated use of telecommunications and informatics. Telematics devices transmit data from an original location to a calculated location and can exert a degree of control over distant targets. Telematics may refer to, for example: sending, receiving and storing information via telecommunication devices in conjunction with control of distant objects; integrating telecommunications and informatics for vehicle applications. In certain embodiments, telematics may include delivery of positioning information that may be provided by a GNSS receiver to a telematics device.

handheld device

A handheld device may refer to, for example, a mobile electronic device. Conventionally, these devices include memory, processors and displays. Handheld devices include, for example, personal digital assistants, personal computers, cellular telephones, smart phones, cameras, handheld radios and televisions, and the like. Handheld devices provide the ability to travel to remote locations. Handheld devices are hand-held, and thus typically have a form factor that is convenient to hold in one hand of an operator and operate with the other hand of the same operator. Handheld devices typically weigh no more than a few pounds and often can weigh only a few pounds.

Example handheld device including electronic control module, fluid analysis control module and telematics unit

FIG. 61 is a diagram of a handheld device 6110 , a fluid analysis control module 6111 , and a telematics device 6113 . Handheld device 6110 may also be coupled with an electronic control module of an asset such as a construction equipment asset, locomotive, vehicle, or the like. Handheld device 6110 is shown removably coupled to fluid source 6150 . The fluid analysis control module 6111 receives a fluid sample 6131 from a fluid sample input 6130 . Fluid sample input 6130 may be a catheter, port, probe or the like permanently or removably coupled to handheld device 6110. Microfluidic analysis can occur within the fluid analysis control module 6111 , eg, via one or more LOCs included in or coupled to the fluid analysis control module 6111 as part of the microfluidic analyzer 6117 . Additionally, the microfluidic analyzer 6117 can perform analyzes such as, but not limited to: mass spectrometry, specific gravity, viscosity, temperature, and/or contaminant detection. After analysis, the fluid analysis control module 6111 sends the analysis results to the telematics device 6113 .

A technician may removably couple the handheld device 6110 to the fluid source 6150 . The fluid source 6150 can be any of various types of fluids, depending on the configuration of the handheld device 6110 and its microfluidic analysis capabilities. In one embodiment, the handheld device 6110 can be removably coupled to a fluid source 6150 disposed in a vehicle or piece of machinery. In another embodiment, the handheld device 6110 can be removably coupled to a fluid source 6150, such as an ocean, lake, river, potable water supply, or any type of water volume. In general, handheld device 6110 can be removably coupled to any source of fluid that is equipped for analysis in a microfluidic assay. It should be appreciated that detachable coupling can include coupling with the hand-held device 6110 and submersion in a fluid source, removably inserting into a fluid source access port, or receiving a provided fluid sample 6131 (e.g., fluid is poured, injected, etc. into a receiving catheter One or more probes, catheters, etc. in

Example handheld telematics microfluidic analysis system

61 is a block diagram of an example of a handheld telematics microfluidic analysis system. According to an embodiment, the fluid analysis control module 6111 is coupled to the telematics device 6113 to provide analysis results to the management system 6120 . FIG. 61 also shows components that may include a fluid analysis control module 6111. In one embodiment, the fluid analysis control module 6111 includes a microfluidic analyzer 6117 (which may include one or more LOCs), an analysis controller 6116 , a results compiler 6114 and a fluid results analyzer 6115 . In certain embodiments, the handheld device 6110 can be removably coupled to a construction equipment asset, locomotive, machine, or vehicle such that the fluid analysis control module and/or analysis controller 6116 can communicate with the electronic control module 6112 . Through this communication, analysis trigger conditions can be provided from the electronic control module 6112 to the handheld device 6110.

In one embodiment, the microfluidic analyzer 6117 receives a fluid sample 6131 from a fluid source 6150 . Fluid source input 6130 may be removably fluidly coupled to fluid source 6150 and operative to allow handheld device 6110 to acquire fluid samples 6131 as desired. Fluid sources 6150 may include, but are not limited to, vehicles, heavy machinery, locomotives, construction equipment, robotic equipment, lakes, ponds, oceans, streams, rivers, bodily fluids, organic or synthetic fluids. In certain embodiments, the microfluidic analyzer 6117 recirculates the fluid sample 6131 into the fluid source 6150 via the fluid sample output 6140 fluidly coupled to the fluid source 6150 . In certain embodiments, the fluid sample 6131 is consumed by microfluidic analysis in the microfluidic analyzer 6117. In other embodiments, microfluidic analyzer 6117 processes excess fluid sample 6131 rather than returning it to fluid source 6150 via fluid sample output 6140 . For example, excess sample not fully consumed by analysis may be stored for subsequent processing by the fluid sample output 6140 in an environmentally inclusive manner.

Fluid analysis control module 6111 also includes analysis controller 6116 that initiates acquisition of fluid sample 6131 by fluid source 6150 and also initiates microfluidic analysis of fluid sample 6131 . Analysis controller 6116 responds to the occurrence of an analysis trigger condition. The analysis trigger may be an internal trigger that occurs within the fluid analysis control module 6111, or the analysis trigger may be an externally received trigger. An analysis trigger condition as an internal trigger condition may include an operational characteristic of the handheld device 6110 coupled to the fluid analysis control module 6111 . Some examples of these internal analysis triggers include, but are not limited to: current time, ambient temperature, elapse of a predetermined period since last sample, handheld 6110 powered on, handheld 6110 powered off, fluid sample 6131 temperature, fluid source 6150 temperature, Fluid sample 6131 pressure and fluid source 6150 pressure. Additionally, the fluid analysis control module 6111 may include instructions to trigger analysis when certain combinations of trigger conditions occur. For example, according to one embodiment, this combination may be an ambient temperature that exceeds a specified threshold (eg, 37.7° Celsius) within a specified period of time (eg, 4 hours) when the handheld device is activated. An example of an external trigger is an instruction received via the telematics device 6113, where the received instruction directs the fluid analysis control module 6111 to sample and analyze a particular fluid. If the handheld device does not possess a fluid sample to be analyzed, the operator of the handheld device 6110 may be directed (e.g., via a graphical user interface) to detachably couple the handheld device 6110 to an appropriate fluid source 6150 so that a fluid sample may be obtained 6131. Another example of an external trigger condition is an instruction received via a keypad or other input device coupled to the handheld device 6110 .

The fluid analysis control module 6111 also includes a fluid results analyzer 6115 . Fluid Results Analyzer 6115 receives results from Results Compiler 6114 . Once the results are received, the fluid results analyzer 6115 immediately provides the data to the analysis controller 6116, the telematics device 6113, or both. In certain embodiments, the result analysis results of the fluidic results analyzer 6115 may include triggering the analysis controller 6116 to direct the microfluidic analyzer 6117 to perform additional microfluidic analyses. For example, in one embodiment, if the result of the microfluidic analysis is that the fluid is reviewed by the Fluid Results Analyzer 6115 and the fluid viscosity is determined to be below an established threshold, then this may trigger a secondary microfluidic analysis of metal particles in the fluid. analyze.

In certain embodiments, the analysis controller 6116 is configured to initiate a first type of analysis of a sample in response to a first analysis trigger and to initiate a second type of analysis of the same sample in response to the occurrence of a second analysis trigger. In certain embodiments, more than two analyzes may be performed in response to various triggering conditions. That is, in certain embodiments, the number of analyzes initiated by the analysis controller 6116 is not limited to two, but instead may be three, four, or more, depending on the number and type of analysis trigger conditions experienced and the duration of the analysis. The microfluidic analysis capability remaining in the fluid analysis control module 6111. In certain embodiments, such as in FIG. 63, the fluid analysis control module 6111 can include more than one microfluidic analyzer. In certain embodiments, the analysis controller 6116 can be configured to initially acquire a second sample for the second type of analysis, rather than analyzing the same sample with two different types of analysis. For example, if the temperature of the fluid exceeds a certain level; then the analysis controller 6116 can be triggered to start an analysis analyzing molecular breakdown and another analysis analyzing fluid particles. In another example, the analysis controller 6116 may analyze the fluid viscosity if the ambient temperature drops below a certain temperature. In another example, if the handheld device 6110 receives an external trigger condition after a certain time of day, the analysis controller 6116 may be triggered and start analyzing the analysis of the fluid particles.

After the microfluidic analyzer 6117 has completed the analysis, it provides the analysis results to the results compiler 6114. Results compiler 6114 is also included in fluid analysis control module 6111. In certain embodiments, the microfluidic analyzer 6117 can perform multiple analyzes and the results compiler 6114 will store and compile the analysis results before providing them to the fluidic results analyzer 6115.

In certain embodiments, agent source 6118 adds agents to microfluidic analyzer 6117 to facilitate certain types of tests. Such agents may be certain types of fluids, or other types of substances necessary to perform the test. The agent can be in a refillable container or can be recycled after each test is completed. In certain embodiments, agent source 6118 is external to fluid analysis control module 6111.

In certain embodiments, fluid samples 6131 may include, but are not limited to, fluids such as: oil, hydraulic fluid, locomotive oil, antifreeze, coolant, transmission fluid, torque converter fluid, clutch fluid, differential fluid , transaxle fluid, transfer case fluid, brake fluid, battery acid, windshield washer fluid, water, fluid chemicals, terpenoids, organic fluids, body fluids, blood or acid.

Figure 62 shows an embodiment of a handheld device 6110 in which the microfluidic analyzer 6117 is detachable. Insertion area 6210 is an orifice that receives an interchangeable microfluidic analyzer 6117 . Since different microfluidic analyzers 6117 can be configured to perform different types of analyses, an operator of handheld device 6110 may wish to swap one microfluidic analyzer 6117 for another. For example, the operator of the handheld device 6110 may perform an analysis using one microfluidic analyzer 6117 to determine the type of debris in the stream, and then, after switching the microfluidic analyzer 6117, perform another analysis to determine the pH in the stream.

FIG. 63 shows an embodiment of a handheld device 6110, wherein the handheld device 6110 includes a plurality of microfluidic analyzers 6117. In certain embodiments, the handheld device 6110 includes a plurality of detachable microfluidic analyzers 6117 and a plurality of insertion regions 6210 . The detachable microfluidic analyzer 6117 can be removed at the end of its operational life and exchanged for a different microfluidic analyzer 6117 offering a different or additional microfluidic analysis technique, and/or can be removed and replaced with a new one. Microfluidic Analyzer 6117 replaced. In other embodiments, the handheld device 6110 includes a plurality of permanent microfluidic analyzers 6117 .

Telematics device providing results to management system

FIG. 61 shows a telematics device 6113 coupled to a fluid analysis control module 6111. In certain embodiments, fluid results analyzer 6115 provides analysis results to telematics device 6113. After the telematics device 6113 receives the analysis results, the telematics device 6113 wirelessly transmits the analysis results to the management system 6120 . It should be appreciated that in some embodiments, analysis results and/or other information received from the telematics device 6113 may be stored in a storage system and/or database of the management system 6120, and that the management system 6120 may receive the telematics device 6113 or from Other reporting sources receive other information about the handset 6110 (as already described herein). In some embodiments, the handheld device 6110 may include a positioning system such as a GNSS receiver 6119 . In these embodiments, a GNSS receiver 6119 can be coupled to the telematics device 6113. In certain embodiments, the telematics device 6113 may include or be communicatively coupled to a positioning system such as a GNSS receiver 6119 . In these embodiments, the telematics device 6113 can report the location of the handheld device 6120 to the management system 6120 independently of or contemporaneously with transmitting the analysis results to the management system 6120. As a non-limiting example, another reporting source coupled to or independent of the handheld device 6110 may provide the location of the handheld device 6110 to the management system 6120 independently of any information provided to the management system 6120 by the telematics device 6113 .

In certain embodiments, the telematics device 6113 provides the results to at least one management system 6120 via radio, microwave, or optical wireless communication means. In certain embodiments, the telematics device 6113 may provide results via a point-to-point link, a broadcast link, or a multipoint link.

In certain embodiments, the management system 6120 includes a result analyzer 6121 . The result analyzer 6121 converts the analysis result into various actions. For example, result analyzer 6121 may include a lookup table or other association mechanism that associates a particular result with a particular action. The results analyzer 6121 may then instruct the management system 6120 to send an alert to each employee, provide the results to one or more reporting sources 208 (which are capable of receiving and reporting), provide the results to one or more receiving devices 5900, according to Remotely received results of fluid analysis to send operational control commands (such as remote power down commands) to assets at risk of damage, remotely power down the handheld device 6110, and/or send operational instructions to the handheld device 6110. The electronic control module 6112 to which the device 6110 is coupled. Receiving device 5900 may be a device such as a cellular telephone, computer, personal digital assistant, pager, or other similar electronic device capable of receiving audio and/or electronic data messages (eg, text, email, text messages). Results can be sent to multiple receiving devices of the same or different types.

It should be appreciated that reporting sources 208 may include any number of reporting sources and reporting source methods, including audio, video, text, Braille, codes, passwords, and the like. For example, reporting sources 208 may include electronic devices, GNSS-enabled devices, machine controllers, video-enabled devices (e.g., camera-enabled handheld devices such as mobile phones with camera/video, PDAs with camera/video, watches with cameras/video, etc.), video cameras, webcams, and the like), human sources, assets being monitored, other assets, and the like. In one embodiment, any or all of the reporting sources 208 can provide asset information to the management system 6120 including one or more of location information, operational information, and status information. For example, in certain embodiments, one or more reporting sources 208 may report operational information, location information, or status information regarding assets or other objects from which management system 6120 receives telematically provided fluid analysis information. These reporting sources 208 are distinct from the previously described telematics device 6113. This information is in addition to any microfluidic analysis information reported remotely to the management system 6120 and may be used in reports generated by the management system 6120 and/or used to make automated decisions regarding fluid sampling.

In certain embodiments, the results analyzer 6121 may instruct the management system 6120 to provide the results to various receiving devices 5900 . For example, the management system 6120 can: send alerts to cellular devices including smart phones and personal digital assistants; send alerts via email to an administrator's computer; or send commands directly to the handheld device 6110. In certain embodiments, results analyzer 6121 may utilize information received from telematics device 6113 and from one or more additional reporting sources in determining an action, such as an alert or notification. For example, if the fluid analysis results received from the telematics device 6113 indicate that the fluid is in an undesired condition, the location of the handheld device 6110 received from the secondary reporting source may be used by the results analyzer 6121 to select the closest location to the handheld device 6110. A mechanic (eg, from an approved mechanic list) to send a maintenance dispatch order.

In some embodiments, the management system 6120 can provide the results to a graphical user interface. In other embodiments, the results may cause the receiving device to modify the behavior or operating characteristics of the handheld device 6110. For example, management system 6120 may remotely direct fluid analysis control module 6111 (or other telematically coupled device located on, coupled to, or associated with handheld device 6110 ) to limit Fluid sampling from fluid source 6150.

Example computer system environment

Referring now to FIG. 1 , all or a portion of certain embodiments described herein consist of computer readable and computer executable instructions residing, for example, in a computer usable/computer readable storage medium of a computer system. That is, FIG. 1 illustrates one example of a type of computer (computer system 100 ) that may be used in accordance with, or may be used to implement, various embodiments discussed herein. It should be appreciated that the computer system 100 of FIG. 1 is merely an example and that implementations as described herein may be implemented on a variety of different computer systems, including but not limited to general purpose computer systems, networked computer systems, embedded computer systems, routers, switches, server devices , client devices, various intermediary devices/nodes, stand-alone computer systems, media centers, handheld computer systems, multimedia devices and the like) or within. The computer system 100 of FIG. 1 is well suited for utilizing local/peripheral tangible computer-readable storage media, such as, for example, RAM 104, ROM 106, and/or storage 118 (which may be, inter alia, or with direct access storage, floppy disks, optical storage disks) , Universal Serial Bus "U" disk, removable memory card).

Example how-to

Referring to Figures 64A-64D, a flowchart 6400 illustrates an exemplary procedure used by various embodiments. Flowchart 6400 includes processes and operations that, in various embodiments, are carried out by one or more of the devices shown in FIG. 61 or via computer system 100 or components thereof.

Although specific procedures are disclosed in flowchart 6400, these procedures are examples. That is, the embodiment is well suited for performing various other operations set forth in the process of flowchart 6400 or variations of the operations described. Also, in some embodiments, the operations in flowchart 6400 may be performed in an order different from that presented, not all operations described in one or more of these flowcharts may be performed, and/or one or more of the operations described in these flowcharts may be added. Multiple additional operations.

The operations of certain exemplary methods of operation of the proposed embodiments are discussed below in detail. Referring to Figures 64A-64D, a flowchart 6400 illustrates an exemplary procedure used by various embodiments. Flowchart 6400 includes certain procedures that, in various embodiments, are carried out by a processor under the control of computer readable and computer executable instructions. In this manner, in various embodiments, the procedures described herein in connection with flowchart 6400 are implemented or can be implemented using a computer. Computer-readable and computer-executable instructions may reside in any tangible computer-readable storage medium, such as, for example, in data storage features (of FIG. 1 ) such as RAM 104, ROM 106, and/or storage 118. Computer readable and computer executable instructions residing on a tangible computer readable storage medium are designed to control or operate in conjunction with, for example, one or some combination of processor 102 or other similar processors. Although specific procedures are disclosed in flowchart 6400, these procedures are examples. That is, the embodiment is well suited for implementing various other procedures or variations of the procedures set forth in flowchart 6400 . Also, in some embodiments, the procedures in flowchart 6400 may be performed in an order different from that presented and/or not all of the procedures described in one or more of Figures 64A-64D may be performed. It should also be appreciated that one or more of the procedures described in flowchart 6400 may be implemented in hardware, or a combination of hardware and firmware, or a combination of hardware and software running on hardware.

64A is a flowchart 6400 of an exemplary method of analyzing a fluid, according to an embodiment. Reference will be made to the elements of FIG. 61 in order to illustrate the method operations of flowchart 6400 . In one embodiment, the method of flowchart 6400 describes the use of microfluidic analyzer 6117 in analyzing fluid sampled from sample source 6150 .

At operation 6410, in one embodiment, the handheld device 6110 receives a fluid sample. In certain embodiments, the analysis controller 6116 detects an analysis trigger condition and begins sample acquisition and microfluidic analysis. For example, an analysis trigger may be an event including, but not limited to: current time, ambient temperature, elapse of a predetermined period of time since the last sample, handheld device 6110 powered on, handheld device 6110 powered off, fluid sample 6131 temperature, fluid source 6150 temperature, Fluid sample 6131 pressure and fluid source 6150 pressure.

At operation 6420, in one embodiment, the microfluidic analyzer 6117 coupled to the handheld device 6110 analyzes the sample.

At operation 6430 , in one embodiment, the microfluidic analyzer 6117 provides analysis results to the telematics device 6113 .

At operation 6440 , in one embodiment, the flowchart 6400 also includes an agent source 6118 that can provide a test agent to the microfluidic analyzer 6117 . For example, microfluidic analyzer 6117 will collect a stream water sample via fluid source 6150 . Agent source 6118 will then provide chemical reagents to microfluidic analyzer 6117 to facilitate a particular type of test within microfluidic analyzer 6117. For example, the chemical reagent may be a solution of sodium nitrite in glycerol, water, and acetic acid to determine the amount of a particular amino acid. As another example, the chemical reagent may be iron(II) sulfate combined with a mineral acid to test for the presence of cyanide. As another example, the chemical reagent may be a solution of hydrochloric acid (HCl) and periodic acid (HIO3), used to detect the presence of glycerol, a major component in antifreeze, and oil.

At operation 6450, in one embodiment, flowchart 6400 further includes performing a first type of analysis of the sample in response to occurrence of a first analysis trigger condition. The trigger condition is detected by the analysis controller 6116 starting the microfluidic analyzer 6117. A second type of analysis of the sample then occurs in response to a second different analysis trigger condition. The analysis controller 6116 also detects a second trigger condition.

At operation 6460 , in one embodiment, the method of flowchart 6400 further includes wirelessly transmitting from the telematics device 6113 the results received from the fluid analysis control module 6111 . In one embodiment, the results are communicated to the management system 6120. For example, transmission of results may occur via radio, microwave or optical transmission.

At operation 6470 , in one embodiment, the result analyzer 6121 automatically compares the received result to result response rules maintained by the management system 6120 . For example, Outcome Analyzer 6121 may look for Outcome Response Rules and cause Management System 6120 to initiate a response.

At operation 6480, in one embodiment, the management system 6120 initiates the response specified by the response rules. For example, responses may include, but are not limited to: displaying analysis information on a GUI to the owner of the handheld device 6110 at a remote location; displaying analysis information to the operator of the handheld device 6110 on the GUI; power on the handheld device 6110; display analysis information on a PDA, cellular device, or other receiver; send remote operational commands to the asset based on the analysis of the asset's fluids; and send messages (audio, text, graphics, and / or email) to the receiving device 5900.

Thus, exemplary embodiments of the inventive subject matter have been described. Although various embodiments of the inventive subject matter have been described in language specific to structural features and/or methodological acts, it is to be understood that the appended claims are not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims and their equivalents.

All elements, parts and steps described herein are preferably included. It is to be understood that any of these elements, parts and steps may be replaced by other elements, parts and steps or deleted altogether as will be apparent to those skilled in the art.

In summary, the following is disclosed herein: A fluid analysis system includes a handheld device and a management system. The handheld device includes a fluid analysis control module and a remote information device. The fluid analysis control module is configured to initiate taking a fluid sample and providing the sample to a microfluidic analyzer for microfluidic analysis. The telematics device is coupled to the fluid analysis control module and constructed with a wireless transceiver. The management system is located remotely from the telematics device and is configured to wirelessly receive the results of the microfluidic analysis transmitted from the telematics device.

concept

The following concepts are presented in this article:

Concept 1. A fluid analysis system comprising:

Handheld devices, which include:

a fluid analysis control module, wherein the fluid analysis control module is configured to initiate collection of a sample of fluid and provide the sample to a microfluidic analyzer for microfluidic analysis; and

a telematics device coupled to the fluid analysis control module and configured with a wireless transceiver; and

A management system located remotely from the telematics device, the management system configured to wirelessly receive the results of the microfluidic analysis transmitted from the telematics device.

Concept 2. The fluid analysis system of Concept 1, further comprising:

An agent source coupled to the fluid analysis control module and configured to provide a test agent for use in the microfluidic analysis.

Concept 3. The fluid analysis system of Concept 1 or 2, further comprising an analysis controller coupled to the fluid analysis control module and configured to initiate the analysis in response to the occurrence of an analysis trigger condition. a first type of analysis of said sample and initiating a second type of analysis of said sample in response to said result of said first type of analysis, wherein said first type of analysis and said second type of analysis are different.

Concept 4. The fluid analysis system of Concept 3 wherein said analysis trigger condition is selected from the group consisting of: altitude of said handheld device, altitude of said handheld device as determined by a Global Navigation Satellite System receiver, geographic location, date, time, user input, ambient temperature, received signals from the vehicle bus, and received signals from the device's internal communication network.

Concept 5. The fluid analysis system of any one of the preceding Concepts, wherein said management system is further configured to receive one or more of operational information and location information from a reporting source other than said telematics device.

Concept 6. The fluid analysis system of any one of the preceding Concepts, wherein said handheld device is configured to removably couple with said microfluidic analyzer.

Concept 7. The fluid analysis system of any one of the preceding Concepts, wherein said handheld device is configured to interchangeably couple with a plurality of different microfluidic analyzers.

Concept 8. The fluid analysis system of any one of Concepts 1 to 5, wherein said hand-held device is coupled to a plurality of microfluidic analyzers performing a process consisting of The analysis of the group: determining the presence of contaminants; determining the type of contaminants; determining the viscosity of the fluid; and determining the temperature of the fluid.

Concept 9. The fluid analysis system of any one of Concepts 1 to 5, wherein said handheld device is selected from the group consisting of: smart phone, cellular phone, personal digital assistant, computer, portable computer, laptop , tablet computer and GNSS receiver unit.

Concept 10. A method for analyzing a fluid comprising:

receiving a sample of fluid at the handheld device;

analyzing the sample, wherein the analysis is performed by a microfluidic analyzer coupled to the handheld device;

providing results of the analysis to a telematics device of the handheld device; and wirelessly transmitting the results from the telematics device for receipt by a management system, the management system being located remotely from the handheld device.

Concept 11. The method of Concept 10, further comprising

A test agent is provided to the microfluidic analyzer from an agent source coupled to the hand-held device.

Concept 12. The method of Concept 10 or Concept 11, further comprising:

automatically comparing said results with result response rules maintained at said management system; and

Initiating a response specified by said result response rule, said response being initiated by said management system.

Concept 13. The method of Concept 10, 11 or 12, wherein said analyzing said sample comprises:

initiating a first type of analysis of said sample in response to occurrence of an analysis trigger condition and initiating a second type of analysis of said sample in response to said result of said first type of analysis, wherein said first type of analysis and The second type of analysis is different.

Concept 14. The method of Concept 13 wherein said analysis trigger condition is selected from the group consisting of: altitude of said handheld device, geographic location of said handheld device as determined by a Global Navigation Satellite System receiver , date, time, user input, ambient temperature, received signals from the vehicle bus, and received signals from the device's internal communication network.

Concept 15. A handheld device comprising:

a fluid analysis control module configured to initiate sampling of the fluid and provide the sample to the microfluidic analyzer for microfluidic analysis; and

A telematics device coupled to the fluid analysis control module and configured with a wireless transceiver for transmitting the results of the analysis to a management system located remotely from the handheld device.

Concept 16. The handheld device of Concept 15, further comprising:

An agent source coupled to the fluid analysis control module and configured to provide a test agent for the analysis of the sample.

Concept 17. The handheld device of Concept 16, further comprising:

A global navigation satellite receiver coupled to the telematics device.

Concept 18. The handheld device of Concept 15, 16 or 17, further comprising an analysis controller coupled to said fluid analysis control module and configured to initiate in response to the occurrence of an analysis trigger condition a first type of analysis of the sample, and in response to the result of the first type of analysis initiating a second type of analysis of the sample, wherein the first type of analysis and the second type of analysis are different.

Concept 19. The handheld device of Concept 18 wherein said analysis trigger condition is selected from the group consisting of: altitude of said handheld device, geographic location of said handheld device as determined by a Global Navigation Satellite System receiver Location, date, time, user input, ambient temperature, signals received from the vehicle bus, and signals received from the device's internal communication network.

Concept 20. The handheld device of Concept 15, 16, 17, 18 or 19 wherein said fluid analysis control module is configured to be removably coupled with said microfluidic analyzer.

Concept 21. The handheld device of Concept 15, 16, 17, 18, 19 or 20, wherein said fluid analysis control module is configured to be interchangeably coupled with a plurality of different microfluidic analyzers.

Concept 22. The hand-held device of any one of the preceding concepts 15 to 21, wherein said fluid analysis control module is coupled to a plurality of microfluidic analyzers performing a process derived from An analysis of the group consisting of: determining the presence of a contaminant; determining the type of contaminant; determining the viscosity of the fluid; and determining the temperature of the fluid.

Claims (22)

1. a fluid analytical systems, it comprises:

Hand-held device, it comprises:

The fluid analysis control module, wherein said fluid analysis control module is configured to start to gather the sample of fluid and described sample is offered to the microfluidic analysis device for carrying out microfluidic analysis; With

The remote information device, it couples with described fluid analysis control module and with together with wireless transceiver is configured in; With

Management system, it is positioned at away from described remote information device part, and described management system is configured to wirelessly receive the result from the described microfluidic analysis of described remote information device transmission.

2. fluid analytical systems according to claim 1, it also comprises:

The agent source, itself and described fluid analysis control module couple and are configured to provide test agent for described microfluidic analysis.

3. fluid analytical systems according to claim 1, it also comprises analyzer-controller, described analyzer-controller and described fluid analysis control module couple, and be configured to the appearance of response analysis trigger condition and start described sample the first kind analysis and respond the described result of described first kind analysis and start the analysis of the Second Type of described sample, the analysis of the wherein said first kind and the analysis of described Second Type are different.

4. fluid analytical systems according to claim 3, wherein said analysis trigger condition choosing is following the group formed freely: the height of described hand-held device, as geographic position, date, time, user's input, the peripheral temperature of hand-held device as described in determined by global navigational satellite system receiver, from vehicle bus, receive signal and receive signal from the internal communication network of device.

5. fluid analytical systems according to claim 1, wherein said management system also is configured to from being not that the report source of described remote information device receives one or more operation information and positional information.

6. fluid analytical systems according to claim 1, wherein said hand-held device is configured to removably with described microfluidic analysis device, couple.

7. fluid analytical systems according to claim 1, wherein said hand-held device is configured to from a plurality of different microfluidic analysis devices, couple interchangeably.

8. fluid analytical systems according to claim 1, wherein said hand-held device and a plurality of microfluidic analysis device couple, and described a plurality of microfluidic analysis devices carry out the freely analysis of following the group formed: determine the existence of pollutant; Determine the type of pollutant; Determine the viscosity of described fluid; With the temperature of determining described fluid.

9. fluid analytical systems according to claim 1, wherein said hand-held device choosing is following the group formed freely: smart phone, cell phone, personal digital assistant, computing machine, portable computer, laptop computer, flat computer and global navigational satellite system receiver device.

10. the method for analysing fluid, it comprises:

Receive the sample of fluid at the hand-held device place;

Analyze described sample, wherein by the microfluidic analysis device coupled with hand-held device, carry out described analysis;

The result of described analysis is offered to the remote information device of described hand-held device; With

Wirelessly transmit described result for being received by management system from described remote information device, described management system is positioned at away from described hand-held device part.

11. method according to claim 10, it also comprises

From the agent source coupled with described hand-held device, test agent is offered to described microfluidic analysis device.

12. method according to claim 10, it also comprises:

Automatic more described result and the rule of response as a result maintained in described management system; With

Beginning is by the response of the described regulation of rule of response as a result, and described response is started by described management system.

13. method according to claim 10, the described sample of wherein said analysis comprises:

The appearance of response analysis trigger condition and start described sample the first kind analysis and respond the described first kind analysis described result and start the analysis of the Second Type of described sample, the analysis of the wherein said first kind and the analysis of described Second Type are different.

14. method according to claim 13, the choosing of wherein said analysis trigger condition is following the group formed freely: the height of described hand-held device, as geographic position, date, time, user's input, the peripheral temperature of hand-held device as described in determined by global navigational satellite system receiver, from vehicle bus, receive signal and receive signal from the internal communication network of device.

15. a hand-held device, it comprises:

The fluid analysis control module, it is configured to start to gather the sample of fluid and described sample is offered to the microfluidic analysis device for carrying out microfluidic analysis; With

The remote information device, itself and described fluid analysis control module couple and are configured in one with wireless transceiver and be used from the result of described analysis is transferred to the management system be positioned at away from described hand-held device part.

16. hand-held device according to claim 15, it also comprises:

The agent source, itself and described fluid analysis control module couple and are configured to provide the described analysis of test agent for described sample.

17. hand-held device according to claim 16, it also comprises:

Global navigation satellite receiver, itself and described remote information device couple.

18. hand-held device according to claim 15, it also comprises analyzer-controller, described analyzer-controller and described fluid analysis control module couple, and be configured to the appearance of response analysis trigger condition and start described sample the first kind analysis and respond the described first kind analysis described result and start the analysis of the Second Type of described sample, the analysis of the wherein said first kind and the analysis of Second Type are different.

19. hand-held device according to claim 18, the choosing of wherein said analysis trigger condition is following the group formed freely: the height of described hand-held device, as geographic position, date, time, user's input, the peripheral temperature of hand-held device as described in determined by global navigational satellite system receiver, from vehicle bus, receive signal and receive signal from the internal communication network of device.

20. hand-held device according to claim 15, wherein said fluid analysis control module is configured to removably with described microfluidic analysis device, couple.

21. hand-held device according to claim 15, wherein said fluid analysis control module is configured to from a plurality of different microfluidic analysis devices, couple interchangeably.

22. hand-held device according to claim 15, wherein said fluid analysis control module and a plurality of microfluidic analysis device couple, and described a plurality of microfluidic analysis devices carry out the freely analysis of following the group formed: determine the existence of pollutant; Determine the type of pollutant; Determine the viscosity of described fluid; With the temperature of determining described fluid.

Images