CROSS REFERENCE TO RELATED APPLICATIONS

[0001] The current application is a PCT patent application, which claims priority to: (1) copending U.S. non-provisional patent application having Serial No. 14/855,371, filed September 15, 2015 and titled "Conditional Proximity Based Equipment Authorization Key"; (2) co-pending U.S. non-provisional patent application having Serial No. 14/657,198, filed March 13, 2015, and titled "Fleet Management System"; (3) co-pending U.S. non- provisional patent application having Serial No. 14/931,848, filed November 3, 2015, and titled "System for Automated Asset Inspection and Maintenance"; (4) co-pending U.S. non- provisional patent application having Serial No. 14/657,231 filed March 13, 2015, titled "Method for Fleet Management"; and (5) co-pending U.S. provisional patent application having Serial No. 62/109,029, filed January 28, 2015, and titled "Fleet Management System." These references are incorporated herein in their entirety.

FIELD

[0002] The present embodiments generally relate to a fleet management methods and systems for tracking real-time inspections of vehicles and maintenance of vehicles, apparatuses for conditional, proximity-based authorization for use of equipment, and methods and systems for inspection and maintenance of mobile assets.

BACKGROUND

[0003] A need exists for systems and methods for an enhanced fleet management system using devices for monitoring inspection and repair status of vehicles.

[0004] A need exists for using at least one wireless communication device, which can be connected by a network, to inspect and service one or more vehicles or fleet owned by a transportation company. [0005] A need exists for real-time vehicle inspection date, pre-trip, post-trip, roadside or ad hoc inspections that include driver information and vehicle data which can be initiated by the driver of a vehicle using a communication device, such as a smart phone, so that vehicle inspections can be performed before, during, and after trips by the vehicle as it moves through different geographically defined communication service regions.

[0006] A need exists for owners of at least one vehicle or vehicle management companies to know when the at least one vehicle could be going out of service and when they can come back into service quickly, efficiently, using executive dashboards that can monitor a plurality of drivers and a plurality vehicles simultaneously.

[0007] With regard to apparatuses for conditional, proximity-based authorization for use of equipment, although various types and forms of keys exist to access equipment and machinery operable by a user, keys in the current state of the art are typically passive items that merely allow for the use of equipment and machinery based upon the presence of the key.

[0008] Advances in technology have made it possible to broaden the function and usage of keys to incorporate various safety and business objectives related to the equipment and machinery.

[0009] For example, a key used to operate a lathe could determine whether the user has been certified for that specific piece of equipment. A key used to start and operate a vehicle could determine whether the user has a valid license, or has fulfilled certain safety tasks.

[0010] In addition to the determining whether certain conditions have been fulfilled, a need exists for a key that can actively disable equipment and machinery when certain conditions have or have not been met. [0011] Further, a need exists for tracking usage of equipment and machinery to determine whether safety and business objectives have been met, in addition to allowing for easy reporting of equipment and machinery use. [0012] A need exists for a system to streamline the process of asset inspection, asset maintenance, and proper documentation while simultaneously providing businesses with a means for ensuring that procedures are being properly followed by employees.

[0013] Moreover, many businesses have a need for, and retain significant numbers of physical assets required in the performance of their primary activities. Often these physical assets are in the form of multiple pieces of machinery with multiple authorized operators.

[0014] For assets such as construction equipment, specialized machinery, transport vehicles, and the like, numerous pieces of data must be tracked. Exemplary data includes information such as inspection records, maintenance needs and history, operator certification, regulatory data, and the like.

[0015] Often, fragmented systems and processes are employed for various business needs. Further, many businesses have difficulty in policing employees to verify that tasks have been properly accomplished, procedures have been properly followed, and documentation for both internal use or for regulatory compliance has been properly detailed.

[0016] The present embodiments meet these needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The detailed description will be better understood in conjunction with the accompanying drawings as follows: [0018] Figure 1 depicts an overview of the fleet management system and equipment useable to implement the same according to one or more embodiments. [0019] Figure 2 depicts at least one inspection device and a driver client device useable with exemplary disclosed methods according to one or more embodiments.

[0020] Figures 3A-3C depict a vehicle maintenance tracker useable with exemplary disclosed methods according to one or more embodiments.

[0021] Figure 4 depicts at least one mechanic client device useable with exemplary disclosed methods according to one or more embodiments. [0022] Figures 5A and 5B depict an administrative processor useable with exemplary disclosed methods according to one or more embodiments.

[0023] Figure 6 depicts at least one customer client device and a vehicle management processor useable with exemplary disclosed methods according to one or more embodiments.

[0024] Figure 7 depicts a dispatcher processor useable with exemplary disclosed methods according to one or more embodiments.

[0025] Figure 8 depicts the exemplary disclosed methods according to one or more embodiments.

[0026] Figure 9 depicts is a block diagram illustrating the components of the apparatus/device for conditional, proximity- based equipment use authorization [0027] The present embodiments are detailed below with reference to the listed Figures.

DESCRIPTION OF EXAMPLE EMBODIMENTS

[0028] Before explaining the present methods and systems in detail, it is to be understood that the methods and systems are not limited to the particular embodiments and that it can be practiced or carried out in various ways. [0029] The embodiments relate to fleet management methods and systems for tracking real-time inspections of at least one vehicle and maintenance of the at least one vehicle using at least one inspection device, which can be connected to a network with an administrative processor.

[0030] The systems and methods for fleet management involves creating a vehicle maintenance tracker for at least one vehicle or a plurality of vehicles in the fleet.

[0031] The systems and methods can involve performing a vehicle inspection on at least one vehicle or a plurality of vehicles using an inspection device to identify services needed on the at least one vehicle and transfer the inspection information into a vehicle maintenance tracker.

[0032] The systems and methods can involve transferring the vehicle inspection information to a mechanic for verification of services needed on the at least one vehicle or the plurality of vehicles and then simultaneously providing a verification of services needed to the vehicle maintenance tracker while automatically generating at least one of: vehicle repair information prioritized by importance of services, wherein the prioritization is determined by at least one of: a driver, a mechanic or a predetermined priority order of importance for services needed stored in the data storage; a schedule for vehicle service prioritized by importance of services needed; and a vehicle return to service date based on a schedule for vehicle service prioritized by importance of services needed.

[0033] The fleet management systems and methods can be used for tracking at least one vehicle or a plurality of vehicles, with each vehicle having a vehicle identification.

[0034] The inspection device can be configured to transmit a vehicle identification number ("VIN"), such as YIN 23434567, and transmit vehicle inspection information, such as dented passenger side front quarter panel, to an administrative processor.

[0035] The inspection device can communicate with the administrative processor, which can further communicate with an administrative data storage connected to the network. [0036] The administrative data storage can be configured to receive vehicle identification and vehicle inspection information into a vehicle maintenance tracker, which can be an executive dashboard of at least one vehicle or of all vehicles in the fleet, which usable for tracking the at least one vehicle or the plurality of vehicles simultaneously.

[0037] The systems and methods can include at least one mechanic device, which can be connected to the network.

[0038] The at least one mechanic device can be configured to automatically receive the vehicle identification and vehicle inspection information from the vehicle maintenance tracker and automatically transmit to the vehicle maintenance tracker at least one of: an acknowledgement of receipt, mechanic inspection information, vehicle repair information, such as this vehicle requires no repair, which can be inputted by a mechanic; the schedule for vehicle service, such as part will be ordered on 2/3/2015 and installed on 2/7/2015, which can be inputted by a mechanic; a vehicle in service date, such as the vehicle will be in service on 2/8/2015, which can be inputted by a mechanic; a vehicle out of service status, such as out of service through 2/7/2015 which can be inputted by a mechanic; and a vehicle return to service date, such as vehicle will be returned to service on 2/9/2015, which can be inputted by a mechanic. In embodiments, the mechanic inputs can be made using the mechanic device.

[0039] The systems and methods can include providing a vehicle maintenance tracker that allows the status, such as inspections and repairs of the at least one vehicle of the plurality of vehicles to be viewed simultaneously. In embodiments, the inspection device, the mechanic device, and combinations thereof can be viewed in real-time simultaneously for the at least one vehicle or the plurality of vehicles.

[0040] The embodiments further relate to fleet management systems and methods that can have a plurality of processors and a plurality of data storages, which can be connected by a network.

[0041] An example of one of the plurality of processors can be an administrative processor having an administrative data storage configured to receive information into the vehicle maintenance tracker in the administrative data storage for performing a pre- trip, post-trip, roadside, or ad-hoc inspection for a vehicle with a vehicle identification.

[0042] A benefit of the invention is that fewer accidents will occur due to systems and methods for a systemized inspection system that is networked directly with mechanics forming a trackable monitoring system for when vehicles are in service or out of service by drivers, fleet owners, or combinations thereof.

[0043] A benefit of the invention can allow the driver or the fleet owner to view all the statuses of all the vehicles simultaneously and in real-time, providing better predictability of vehicles for being in service with more predictable revenue generation.

[0044] The term "fleet management system" as used herein can refer to systems and methods for managing a group of transportation vehicles or cargo vehicles, such as a taxi cab fleet, a tractor trailer fleet, other commercial motor vehicles (CMV), or a fleet of government vehicles. In embodiments, the system can manage a group of, but is not limited to, golf carts, boats, unmanned drones, or other types of recreational vehicles.

[0045] The term "inspection" as used herein can refer to a pre-trip inspection, a roadside inspection, a post-trip inspection or an ad-hoc inspection. In embodiments, the term inspection can include driver information, vehicle identification and vehicle inspection information, which can be initiated by the driver of the at least one vehicle using a communication device, so that vehicle inspections can be performed before, during, and after trips.

[0046] The term "administrative processor" as used herein can refer to a laptop, a computer, a portable hand held device, such as a cellular phone or a tablet computer, combinations thereof, or any device capable of at least two way communications. The administrative processor can communicate with at least one display.

[0047] The term "inspection device" as used herein can refer to a device which can be portable, such as a cellular phone, a camera, a tablet computer, a combination of digital input devices which enable both words and images to be captured simultaneously for a vehicle, or the like. The inspection device can be operated by an individual, such as a driver of a vehicle or a safety manager of a vehicle. In embodiments, the inspection device can be the mechanic device and/or the customer client device. The inspection device can have a plurality of sensors attached to a processor capable of bidirectional communication, such as an inspection robot. In embodiments, the inspection devices can be directly mounted on the vehicle and adapted to communicate with the vehicle onboard computer system to provide mileage, fuel usage, diagnostic information, routine maintenance information and accident information. The inspection device can communicate with at least one display. [0048] The term "mechanic device" as used herein can refer to a device, which can be portable, such as a cellular phone, a camera, a tablet computer, a combination of digital input devices which enable both words and images to be captured simultaneously for a vehicle, the like or combinations thereof. The mechanic device can be operated by an individual, such as a mechanic. The mechanic device can communicate with at least one display.

[0049] The term "customer client device" used herein can refer to a portable device, such as a cellular phone, a laptop, a desk top computer, a tablet, a personal communication, combinations thereof, or any device capable of at least two way communications. In embodiments, the customer client device can be the inspection device and/or the mechanic device. The customer client device can be operated by an individual, such as a fleet owner, an employee of a company, or safety manager. The customer client device can be capable of bidirectional communication. The customer client device can have a sufficient memory storage area to allow a customer to view information from the at least one vehicle or all vehicles in a fleet simultaneously, or in priority grouping including information on vehicle mileage, fuel usage, diagnostic information, routine maintenance information and accident information from the vehicle maintenance tracker. The customer client device can store a vehicle maintenance tracker locally for periodic synchronization, or access a central vehicle maintenance tracker.

[0050] The term "data storage" as used herein can refer to a non-transitory computer readable medium, such as a hard disk drive, solid state drive, flash drive, tape drive, and the like. The term "non-transitory computer readable medium" excludes any transitory signals but includes any non-transitory data storage circuitry, e.g., buffers, cache, and queues, within transceivers of transitory signals.

[0051] The term "dispatcher processor" as used herein can refer to a processing device which can be operated by a fleet dispatcher. In some instances, the dispatcher processor can be a cellular phone, a laptop, a desk top computer, a tablet computer, a personal communication device capable of processing, and combinations thereof. In embodiments, the dispatcher processor can be capable of at least two way communications. [0052] The term "document storage" as used herein can refer to a storage area where all collected data from the system can be stored. The data can be stored on at least one of the data storages in at least one of the processors and can be accessible on at least one of the devices according to assignments determined by management. All documentation that can be collected throughout the system can be sorted in the driver or vehicle categories. The document storage can sort all data according to processes that collected the information to allow for a streamlined retrieval process. The document storage can also be capable of capturing photos for items needed.

[0053] Document storage can store any pertinent vehicle or driver information. A non- exhaustive list of documents includes driver input logs, log books, inspection videos and reports, accident reports, accident history, delivery schedules, delivery receipts, bills of lading, job histories, fuel receipts, fuel logs, mileage logs, odometer readings, location information, drivers licenses, driver medical information, driver certifications, repair receipts and logs, insurance information, vehicle registration information, vehicle permits, and the like. The document storage is a repository for storing pertinent information in a single, easily accessible, and organized location.

[0054] The term "driver" as used herein can refer to a human that operates a vehicle that provides transportation, cargo, or remote viewing, such as a pilot of a drone. A driver can be a truck driver, a pilot of a commercial aircraft, a car driver, a cab driver, a boat driver, a captain. In embodiments, a driver can include a robot with artificial intelligence, such as onboard computers of cars that drive, or park themselves. [0055] The term "accident tracker" as used herein can refer to a step by step process to instruct the driver through correct procedures when an accident occurs. The accident tracker program can consist of the following do not admit fault, check for injuries, call dispatch/911, take video/photos of location and property damage, gather information on person(s) involved and witness(es) involved, take photos/video of others involved in accident, record video of person(s) and witness(es) involved, and accident loss description. Once each step is complete, the accident tracker can create an electronic claim summary file that can be emailed to management, a safety manager, a mechanic, or combinations thereof and can be stored in at least one of the plurality of processors. The benefit of the accident tracker is to provide simple steps to follow each time an accident occurs to assure reporting details can be completed accurately and includes all the details needed to sure up the claims handling process.

[0056] The term "driver fuel usage tracker" as used herein can refer to a part of the system that can track the amount of fuel used by a vehicle and the mileage at the time of refueling. This information can then be used to calculate the fuel usage per mile. When a vehicle is refueled, the driver can input the amount of fuel used. The inspection device can create a date and time stamp. In embodiments, the inspection device can be capable of capturing a photo of the receipt, but is not necessary.

[0057] The term "driver log book" as used herein can refer a log book that can be used in conjunction with the statuses and can be used to track the time spent in one category, such as off-duty, sleeper birth, driving, and on-duty not driving. The driver, dispatcher, safety director, manager, or combinations thereof can access the log book for the driver. In embodiments, the driver log book can be presented in a format permissible by governmental entities. When the driver log book is viewed, it can indicate the amount of time spent in each category.

[0058] The term "global positioning system" as used herein can refer to a satellite navigation system that provides location and time information in all weather conditions, anywhere on or near the Earth where there is an unobstructed line of sight to four or more GPS satellites or a triangulation system using cellular network allowing client devices locations to be determined using vectors from cellular towers, based on Wi-Fi signals or other similar types of networks. [0059] The term "log book status" as used herein can refer to a driver status as recorded in the log book in the administrative data storage. Log book status can be on-duty, off-duty, driving or sleeping. [0060] In embodiments, the at least inspection device can include computer instructions to instruct the inspection processor to transmit a location of the inspection device and compare the transmitted location to the global positioning system using either the administrative processor or the inspection device, wherein the compared location information is then transmitted to the inspection device, the administrative data storage or combinations thereof.

[0061] In other embodiments, systems and methods for fleet management can transmit a location of at least one vehicle, the inspection device, or combinations thereof and compare the transmitted location to the global positioning system using either the administrative processor or the inspection device, wherein the compared location information is then transmitted to the inspection device, the administrative data storage, the customer client device or combinations thereof. In this embodiments, the global positioning system can be used to compare the transmitted location to the log book status, which can in tum validate the driver log book, the log book status and the location of the at least one vehicle, the inspection device, or combinations thereof.

[0062] The term "network" as used herein can refer to a global communication network, the internet, a cellular network, a local area network, a wide area network, a peer to peer network, a satellite network, a global positioning system or combinations thereof.

[0063] In embodiments, the term "repair tracker" can provide a tracker with digital graphic elements that can be displayed on the inspection device, the mechanic device, the customer client device, or combinations thereof, which can provide indications and updates regarding repairs done at the time of service or inspection of the vehicle.

[0064] The term "at least one safety class or safety classes" as used herein can refer to at least one safety class, such as a virtual safety class, which can be transmitted to an inspection device for viewing and requiring a response from a person, such as a driver, as a result of viewing the safety class. The at least one safety class can be directed to vehicle braking techniques, use of mirrors, loading of vehicles, site awareness, drug and alcohol usage while driving, sleep apnea awareness, monitoring of fuel usage, what to do in the event of an accident and similar topics. The at least one safety class can also incorporate a safety assessment or a safety exam or test for the driver or viewer.

[0065] The term "vehicle or vehicles" as used herein can refer to at least one vehicle, which in embodiments can be a manned vehicle. In embodiments, the term "vehicles" can also refer to an unmanned vehicle. In embodiments, the term "vehicles" can refer to a plurality of vehicles, such as a fleet of vehicles. The term "vehicles" can refer to a moveable object which can be self-propelled and which can transport persons, gear, materials, and products, or vehicles which can act as surveillance vehicles.

[0066] The term "vehicle identification" as used herein can refer to a number, such as a VIN for a car, an alpha- numerical combination, a boat name, symbols, or color indicator for a vehicle, such as "red truck or blue truck". Vehicle identification can be in the form of a bar code, QR code, an electronic identifier, such as an RFID chip or a frequency. Vehicle identification can include a VIN number, assigned vehicle number, a make of vehicle, such as a truck or a trailer, a power supply, a model, a year of manufacture and additional details, such as weight or rating can be included.

[0067] The term "vehicle inspection information" as used herein can refer to inspection of the status of the vehicle, such as condition and operability, such as driver side headlight light out, slow oil leak, spare is flat, reflective tape is gone, mud flaps are damaged, body panels are damaged, frame is cracked, and windshield is cracked. In embodiments, the vehicle inspection information can include an electronic driver vehicle inspection report, such as an EDVIR, E-DVIR or DVIR.

[0068] The term "vehicle mileage tracker" as used herein can refer to a part of fleet management systems and methods that can track and calculate the vehicle mileage. The driver can input the mileage at predetermined points such as at the time of fueling, crossing state lines, and/or arrival or departure from delivery or terminal locations. The vehicle mileage tracker can then report this information back to at least one of the processor. [0069] In embodiments, a trip meter can be used which can have an elapsed time to show how much time is left until the driver needs to be put out of service.

[0070] The term "vehicle trip status" as used herein can refer to a part of the system that can capture the vehicle location and current status. The status can be updated by the driver and the inspection device communicates the information to dispatch and management, such as to the customer client device. The descriptions used within the vehicle trip status program can include, but is not limited to: off duty, post trip, pre trip, arrived, waiting, waiting with off-duty exemption, in-route, on duty and problem. Each time the status is changed by the driver, the dispatch, management, or combinations thereof can be notified, such as through the customer client device. The vehicle trip status can be used in conjunction with the driver log book to update the log book for the following categories, which include, but are not limited to: off duty, sleeper birth, driving, and on duty not driving. [0071] The term "work status" when referring to the driver can refer to one of the following: a driver in route, a driver is starting a route, a driver is completing a route, a driver is waiting while en-route, a driver is out of service due to mechanical difficulties. For example, a driver of a tractor trailer indicates on Tuesday, February 10, 2015 at 5:55 pm he is waiting while en-route to deliver beach chairs to a store in Maine due to a snowstorm. Work status can include a driver has "arrived". Work status can include that the driver is experiencing a problem, such as a tire blow out.

[0072] The term "work status change" as used herein can refer to the point in time when a driver changes status for example, a driver can change status from driver en-route to driver waiting, or driver starting route changes to driver has completed route, or the status driver can be waiting while en-route has a work status change when driver is out of service due to mechanical difficulties.

[0073] The various devices discussed above, such as the inspection device, the mechanic device, or the customer client device can comprise a means for the user of the device to be tracked. This tracking can be accomplished by means of a login and unique password for each user, or can require identity verification upon a user of the device performing an action or to allow a user access to the device. The identity verification can be the entry of a password, a signature by the user, a biometric identification such as a thumbprint or a retinal scan, or any reasonable process for verifying the user of the device.

[0074] Turning now to the Figures, Figure 1 depicts an overview of equipment needed to implement the fleet management systems and methods according to one or more embodiments.

[0075] The fleet management system 6 can have a plurality of processors and a plurality of data storages.

[0076] In embodiments, the at least one processor can be a computer, a laptop, a desk top computer, a client device, such as a cellular telephone or a smart phone, a tablet computer, or a similar device capable of at least two way communications.

[0077] The fleet management system 6 can have an administrative processor 10 in communication with an administrative data storage 12 via a network 14.

[0078] At least one inspection device 16a and 16b can be in communication with the administrative processor 10 via the network 14.

[0079] At least one mechanic device 24a, 24b, 24c and 24d can be in communication with the administrative processor 10 via the network 14.

[0080] In embodiments, the administrative processor 10 can communicate directly to or through the network 14 to a dispatcher processor 32 and to a vehicle management processor 30.

[0081] The at least one inspection device 16a can be used for inspecting a first vehicle 20a and the at least one inspection device 16b can be used for inspecting a second vehicle 20b.

[0082] The at least one inspection device 16a can be configured to receive and transmit to the administrative processor a driver identification and a vehicle identification for a vehicle. [0083] The at least one inspection device 16a can be configured to collect and transmit to the administrative processor 10 the driver identification, the vehicle identification, and the vehicle inspection information. [0084] In embodiments, the vehicle management processor 30 can communicate directly with the network 14.

[0085] In embodiments, the dispatcher processor 32 can communicate with the administrative processor 10 and the vehicle management processor 30.

[0086] In embodiments, the at least one inspection device 16a can communication with a global positioning system 8, which can communicate with the administrative processor 10.

[0087] Figure 2 depicts the at least one inspection device useable with methods and systems according to one or more embodiments.

[0088] The at least one inspection device 16a is depicted with an inspection display 40 and an inspection processor 42, which can be connected to the inspection display 40. The inspection processor 42 can also communicate with an inspection data storage 44.

[0089] In other embodiments, the inspection processor 42 can communicate directly with the administrative processor.

[0090] The inspection data storage 44 can contain vehicle identification 45, a vehicle maintenance tracker 50, an accident tracker 80, a driver fuel usage tracker 82, a vehicle mileage tracker 84, a driver log book 86, a vehicle trip status 88, and document storage 90.

[0091] The at least one inspection device 16a can include computer instructions 206 to instruct the inspection processor to transmit a location of the inspection device and compare the transmitted location to the global positioning system using either the administrative processor or the inspection device, wherein the compared location information is then transmitted to the inspection device, the administrative data storage or combinations thereof. [0092] The fleet management systems and methods can further comprise computer instructions 207 to compile and store location information continuously or periodically to calculate a total traveled distance per time period, per trip, or other defined interval. This information can further be analyzed and presented in various formats as desired. For example, the administrative data storage can comprise computer instructions 208 to calculate the distance traveled within a jurisdiction, which can be a defined geographical area. The geographical area can be defined by a user of the fleet management system for desired information, and may include areas such as countries, states, counties, or any other area designation.

[0093] Figures 3A-3C depict a vehicle maintenance tracker useable with methods and systems according to one or more embodiments.

[0094] The vehicle maintenance tracker 50 can be stored in either the inspection device or in the administrative data storage of the administrative processor. In embodiments wherein there is a central maintenance tracker in the administrative data storage, the inspection device can access and display information from the maintenance tracker.

[0095] The inspection device or the administrative data storage can be configured to receive information into the vehicle maintenance tracker 50 for performing at least one of: a pre-trip inspection, a roadside inspection, a post-trip inspection, or an ad-hoc inspection for a vehicle with a vehicle identification.

[0096] Figure 3A provides a detail of the vehicle maintenance tracker 50 for performing a pre-trip inspection 51.

[0097] The vehicle maintenance tracker 50 can maintain vehicle identification 45 and a driver identification 47. [0098] Driver identification 47 can include but is not limited to a driver's name, a driver's address, a driver's license number, a state the driver's license is issued in, an employee number, and combinations thereof. [0099] The vehicle maintenance tracker 50 can include, but is not limited to a pre-trip time stamp 52, a pre-trip list of inspection points 53, a pre-trip stored list of repair requests 54, a pre-trip alert for needed repairs based on stored list of repair requests 55, a pre- trip vehicle out of service date 56, and pre-trip alerts that the vehicle is repaired and ready for service 57.

[00100] In embodiments, the vehicle maintenance tracker can be created from computer instructions in the administrative data storage that stores the information and instructs at least one of the processors to generate the following: the inspection with a time stamp, a list of inspection points, a stored list of repair requests, an alert for needed repairs based on the stored list of repair requests, a vehicle out of service date, and an alert that a vehicle is repaired and ready for service.

[00101] Figure 3B provides a detail of the vehicle maintenance tracker 50 for performing a roadside inspection 58.

[00102] The vehicle maintenance tracker can maintain the vehicle identification 45 and the driver identification 47. [00103] The vehicle maintenance tracker can include, but is not limited to a roadside time stamp 59, a roadside list of inspection points 60, a roadside stored list of repair requests 61, a roadside alert for needed repairs based on stored list of repair requests 62, a roadside vehicle out of service date 63, and roadside alerts that the vehicle is repaired and ready for service 64.

[00104] Figure 3C provides a detail of the vehicle maintenance tracker 50 for performing a post-trip inspection 65.

[00105] The vehicle maintenance tracker 50 can maintain the vehicle identification 45 and the driver identification 47.

[00106] The vehicle maintenance tracker 50 can include, but is not limited to a post-trip time stamp 66, a post-trip list of inspection points 67, a post-trip stored list of repair requests 68, a post-trip alert for needed repairs based on stored list of repair requests 69, a post-trip vehicle out of service date 70, and post-trip alerts that the vehicle is repaired and ready for service 71.

[00107] In embodiments, the ad-hoc inspection can be done at any time, such as at the time of the pre-trip inspection, the roadside inspection, the post-trip inspection, or combinations thereof.

[00108] In embodiments, the administrative data storage and the mechanic device can be configured to receive information into the mechanic maintenance tracker in the administrative data storage regarding maintenance performed for the at least one vehicle with vehicle identification using at least one of: the pre-trip inspection, the post-trip inspection, the roadside inspection, the ad-hoc inspection, or combinations thereof.

[00109] In embodiments, the administrative data storage and the mechanic device can be configured to use computer instructions in the administrative data storage to instruct at least one of the processors to generate an alert when the vehicle with the vehicle identification is repaired.

[00110] Figure 4 depicts the at least one mechanic device useable with methods and systems according to one or more embodiments.

[00111] The mechanic device 24a can have a mechanic display 100 and a mechanic processor 102, which can be in communication with a mechanic data storage 104. [00112] The mechanic data storage 104 can include, but is not limited to the vehicle identification 45, the driver identification 47, a pre-trip alert for needed repairs based on stored list of repair requests 55, a roadside alert for needed repairs based on stored list of repair requests 62, a post-trip alert for needed repairs based on stored list of repair requests 69, and an ad-hoc alert for needed repairs based on stored list of repair requests 101.

[00113] The mechanic data storage 104 can contain a mechanic repair initiation 106 and a mechanic inspection initiation 108. [00114] The mechanic data storage 104 can include a schedule of repairs by the mechanic 112, a projected vehicle return to service date 114, and mechanic identification 116.

[00115] In embodiments, the at least one mechanic device can be connected to the network, and the at least one mechanic device can be configured to receive and transmit to the administrative processor the mechanic identification 116 and the vehicle identification 45. In embodiments, the at least one mechanic device can be configured to collect and transmit to the administrative processor: (i) vehicle repair information for the vehicle identification; (ii) vehicle in service dates for the vehicle identification; (iii) vehicle out of service dates for the vehicle identification; and (iv) vehicle return to service dates for the vehicle identification.

[00116] In embodiments, the mechanic device can store information about a mechanic repair initiation date and a vehicle return to service date. The mechanic data storage can include computer instructions to generate and transmit or display a mechanic generated alert 110.

[00117] Figures 5A and 5B depict an administrative processor u seable with methods and systems according to one or more embodiments.

[00118] The administrative processor 10 can be connected to or in communication with an administrative display 11 and the administrative data storage 12.

[00119] The administrative data storage 12 can include but is not limited to the vehicle identification 45, the driver identification 47, the vehicle maintenance tracker 50, the pre- trip alert for needed repairs based on stored list of repair requests 55, the roadside alert for needed repairs based on stored list of repair requests 62, the post-trip alert for needed repairs based on stored list of repair requests 69, the ad-hoc alert for needed repairs based on stored list of repair requests 101, the accident tracker 80, the driver fuel usage tracker 82, the vehicle mileage tracker 84, the driver log book 86, the vehicle trip status 88, and document storage 90.

[00120] The administrative data storage 12 can also comprise an application program interface ("API") 13, to allow separate computer programs to access the data within. For example an API could allow accounting programs to access billable hours or cost information, the API could allow enterprise resource planning software to access repair information. Any computer program needing data from the fleet management system can be granted access and permissions through the API.

[00121] In embodiments, the driver log book 86 can be stored on the administrative data storage, the at least one of the inspection device or combinations thereof.

[00122] The driver log book 86 can be software, which can include computer instructions configured to automatically update as a driver of a vehicle of the fleet management system changes work status and automatically converts the work status of the driver to a log book status and stores the log book status, and wherein the at least one inspection device or the administrative data storage can be configured to record a location and time of work status change. In this embodiment, the at least one vehicle of the fleet management system can automatically communicate using the network, indicating a status as: on duty, off duty, driving or sleeping which can then recorded in the driver log book.

[00123] The administrative data storage can contain computer instructions to instruct the processor to generate the alert or the alerts when the vehicle is repaired and ready for service. In embodiments, computer instructions can be stored in the mechanic data storage, located in the mechanic device. In other embodiments, computers instructions can be stored in any of the data storages and are not limited to any single data storage.

[00124] The administrative data storage 12 can contain the mechanic generated alert 110. In embodiments, the mechanic generated alert can be stored in the administrative data storage once the mechanic generated alert is transmitted.

[00125] In embodiments, the administrative data storage can include but is not limited to the mechanic repair initiation 106, the mechanic inspection initiation 108, the schedule of repairs by the mechanic 112, the projected vehicle return to service date 114, a mechanic identification 116, and a vehicle management identification 120. [00126] In embodiments, the administrative data storage can contain computer instructions 124 to instruct the administrative processor to generate an alert that the schedule of repairs won't be met. [00127] The administrative data storage 12 can contain computer instructions 202 to instruct the administrative processor to transmit or display the mechanic generated alert when the vehicle is repaired and ready for service.

[00128] In other embodiments, computer instructions 202 can be stored in the mechanic data storage, located in the mechanic device. In other embodiments, computers instructions 202 can be stored in any of the data storages and are not limited to any single data storage.

[00129] In embodiments, the mechanic generated alert can be generated by the at least one mechanic device and transmitted or displayed to the at least one of the inspection device, the at least one customer client device, or combinations thereof.

[00130] The administrative data storage can contain computer instructions 204 to instruct the administrative processor to generate an alert or a plurality of alerts when the vehicle is repaired and ready for service. In embodiments, the generated alert can be transmitted by the fleet management system to the at least one of the inspection device, the at least one customer client device, at least one mechanic device, or combinations thereof.

[00131] In other embodiments, computer instructions 204 can be stored in the mechanic data storage, located in the mechanic device. In other embodiments, computers instructions 204 can be stored in any of the data storages and are not limited to any single data storage.

[00132] In embodiments, the administrative data storage 12 can contain computer instructions 355 to instruct the administrative processor to generate a repair tracker for all vehicles using the vehicle maintenance tracker and the mechanic device.

[00133] In embodiments, the administrative data storage 12 can contain at least one safety class 360. [00134] The administrative data storage 12 can contain computer instructions 362 to instruct the administrative processor to transmit the at least one safety class to the at least one inspection device from the administrative data storage. [00135] In embodiments, the computer instructions can instruct the administrative processor to display class materials, such as photos, text, video, audio and the like. In embodiments, the computer instructions can instruct the administrative processor to provide tests and requirements, such as state motor vehicle tests and requirements. [00136] The administrative data storage 12 can contain computer instructions 364 to instruct the administrative processor to record the progress and completion of the at least one safety class by the driver. In embodiments, these computer instructions can present a gauge or meter for one or more drivers showing a percentage of completeness of the least one class on the administrative display.

[00137] In embodiments, a clock can be used showing how much time is left for the driver to complete the at least one safety class without having to restart the class.

[00138] The administrative data storage 12 can contain computer instructions 366 to instruct the administrative processor to transmit the at least one safety class to the at least one customer client device of an owner, a dispatcher, a safety manager, an employee of a company with drivers and vehicles, or combinations thereof from the administrative data storage. [00139] The administrative data storage 12 can contain computer instructions 368 to instruct the administrative processor to record the progress and completion of the at least one safety class by the owner, the dispatcher, the safety manager, the employee of a company with drivers and vehicles, or combinations thereof. [00140] In embodiments, the administrative data storage 12 can contain at least one safety class 360.

[00141] Figure 6 depicts a customer client device useable with methods and systems according to one or more embodiments. [00142] The customer client device 29 can be connected to or in communication with a vehicle management display 31, a vehicle management processor 30 with a vehicle management data storage 119. [00143] In embodiments, the vehicle management processor 30 can be controlled by the transportation company or the owner of the vehicles being maintained and inspected.

[00144] The vehicle management data storage 119 can include but is not limited to the vehicle identification 45, the driver identification 47, the vehicle maintenance tracker 50, the pre-trip alert for needed repairs based on stored list of repair requests 55, the roadside alert for needed repairs based on stored list of repair requests 62, the post-trip alert for needed repairs based on stored list of repair requests 69, the ad-hoc alert for needed repairs based on stored list of repair requests 101, the accident tracker 80, the driver fuel usage tracker 82, the vehicle mileage tracker 84, the driver log book 86, the vehicle trip status 88, and document storage 90.

[00145] The vehicle management data storage 119 can include but is not limited to the mechanic repair initiation 106, the mechanic inspection initiation 108, the schedule of repairs by the mechanic 112, the projected vehicle return to service date 114, the mechanic identification 116, and the vehicle management identification 120.

[00146] In embodiments, the vehicle management data storage 119 can contain the mechanic generated alert 110. [00147] The vehicle management data storage 119 can contain computer instructions 124 to instruct the vehicle management processor 30 to generate an alert that the schedule of repairs will not be met.

[00148] The vehicle management data storage 119 can contain computer instructions 124 to instruct the vehicle management processor 30 to generate an alert that the schedule of repairs won't be met. [00149] The vehicle management data storage 119 can contain computer instructions 125 to instruct the vehicle management processor 30 to generate and transmit or display an alert when the at least one vehicle is repaired and ready for service. [00150] The vehicle management data storage 119 can contain computer instructions 126 computer instructions 126 to instruct the vehicle management processor to generate and transmit or display a vehicle return to service date.

[00151] Figure 7 depicts a dispatcher processor useable with methods and systems according to one or more embodiments.

[00152] The dispatcher processor 32 can be connected to or in communication with a dispatcher display 33 and a dispatcher data storage 99. [00153] The dispatcher data storage 99 can contain, but is not limited to the vehicle identification 45, the driver identification 47, the pre-trip alert for needed repairs based on stored list of repair requests 55, the roadside alert for needed repairs based on stored list of repair requests 62, the post-trip alert for needed repairs based on stored list of repair requests 69, and the ad-hoc alert for needed repairs based on stored list of repair requests 101.

[00154] The dispatcher data storage 99 can contain, but is not limited to the pre-trip alerts that the vehicle is repaired and ready for service 57, the roadside alerts that the vehicle is repaired and ready for service 64, the post-trip alerts that the vehicle is repaired and ready for service 71, and the ad-hoc alerts that the vehicle is repaired and ready for service 103.

[00155] The dispatcher data storage 99 can contain the projected vehicle return to service date 114. [00156] In embodiments, at least one of the data storages can produce an executive dashboard, which can monitor and display vehicle speed tracking, vehicle starts and stops, vehicle acceleration, predictive modeling on accidents for this vehicle based on acceleration, starts, stops, sustained speeds, deceleration, and provide a comparison of quantities of vehicle performed right turns vs. vehicle performed left turns. [00157] In embodiments, the executive dashboard can monitor and display vehicle information simultaneously to the at least one inspection device, the at least one customer client devices, or combinations thereof. In embodiments, the information being monitored and displayed can then be recorded on or save in at least one data storage, such as the administrative data storage.

[00158] As an illustrative example to use the fleet management system, each driver of the fleet can have an inspection device, such as a cellular phone. The driver can input a vehicle identification number, which for this company is Gorilla 1234AA. The driver can also perform a pre-trip inspection looking at, but not limited to tire pressure, tire tread depth, lights all operating, presence or lack of reflective tape, oil pressure, fuel level, oil leaks, and presence or lack of mudguards, brake line condition using the software application on his cellular phone, and combinations thereof. The driver can identify that a front high beam light is not operating and then can transmit the entire inspection information to the administrative processor using the network.

[00159] The administrative processor can be owned and controlled by the fleet management company. The vehicle inspection information along with the vehicle identification can be stored in the vehicle maintenance tracker in the administrative data storage associated with the administrative processor.

[00160] In this example, three mechanics each with a device can be in communication with the administrative processor. The administrative processor can select one of the three mechanics and automatically transmit the vehicle inspection information to the mechanic device, such as a cellular phone.

[00161] The mechanic device can then automatically transmit a schedule for vehicle service to the vehicle maintenance tracker. [00162] The schedule for vehicle service can be displayed on the vehicle maintenance tracker, which can be viewed by the driver with the inspection device at the same time as the mechanic for real-time, simultaneous viewing concerning the vehicle. [00163] Figure 8 depicts the method according to one or more embodiments.

[00164] The method can include forming a vehicle maintenance tracker for the at least one vehicle and storing the vehicle maintenance tracker in an administrative data storage, as illustrated by box 802.

[00165] The method can include performing a vehicle inspection on the at least one vehicle using an inspection device connected to a network to form vehicle inspection information, as illustrated by box 804.

[00166] The method can include identifying services needed on the at least one vehicle, as illustrated by box 806.

[00167] The method can include transferring the vehicle inspection information from the inspection device to the vehicle maintenance tracker, as illustrated by box 808.

[00168] The method can include transferring the vehicle inspection information to a mechanic for verification of services needed on the at least one vehicle, as illustrated by box 810.

[00169] The method can include providing to the vehicle maintenance tracker from the mechanic at least one of: an acknowledgment, mechanic inspection information, vehicle repair information, a schedule for vehicle service, a vehicle in service date, a vehicle out of service status, and a vehicle return to service date based on the schedule for vehicle service, as illustrated by box 812.

[00170] The method can include forming an accident tracker and receiving accident information from at least one of: a driver, the at least one vehicle, or an accident related third party and communicating the accident information to the vehicle maintenance tracker, as illustrated by box 828. [00171] The method can include forming a driver fuel usage tracker and receiving driver fuel usage information from at least one of: a driver, the at least one vehicle, or a fuel dispensing party and communicating the driver fuel usage information to the vehicle maintenance tracker, as illustrated by box 830.

[00172] The method can include connecting a global positioning system to the driver fuel usage tracker, which can be used to validate a driver fuel usage, as illustrated by box 832. [00173] The method can include forming a vehicle mileage tracker and receiving vehicle miles traveled information for the at least one vehicle from at least one of: a driver or the at least one vehicle and communicating the vehicle miles traveled information to the vehicle maintenance tracker, as illustrated by box 834. [00174] The method can include connecting a global positioning system to the vehicle mileage tracker, which can be used to validate a vehicle location, as illustrated by box 836.

[00175] The method can include calculating a traveled distance for a jurisdiction, wherein the jurisdiction is a defined geographic area, as illustrated by box 838.

[00176] For example, the vehicle mileage tracker can have record of the total miles traveled by a specific vehicle. The global positioning system can be used to determine a vehicle location during the times of travel. When a specific geographic area or jurisdiction is specified, this information can be used in conjunction to calculate the miles traveled in that jurisdiction.

[00177] The method can include forming a driver log book, wherein the driver log book can communicate with the vehicle maintenance tracker to track and record a change in a work status of a driver, as illustrated by box 840.

[00178] The method can include forming document storage, for storing documents related to the at least one vehicle, as illustrated by box 842. [00179] As another illustrative example of the method, the method can include performing a vehicle inspection on an airplane, by inspecting the engine and the passenger compartment using an inspection device and identifying that the engine starter, engine alternator, and engine mounts need to be replaced on the engine and that three seats need to be recovered due to tears, which is the vehicle inspection information identifying the type of services needed on the vehicle.

[00180] The method can involve transferring the engine and seat information as vehicle inspection information from the inspection device into the vehicle maintenance tracker in the administrative data storage using the network while simultaneously prioritizing the types of services needed. In this case, the repair of the engine can be listed as a group 1 priority and the seat repairs can be listed as a group 2 priority.

[00181] The method can include transferring the group 1 and group 2 prioritized types of services needed on the vehicle to the mechanic for verification of the types of services. The mechanic can use a networked camera to verify the group 1 services, which are of a higher priority than group 2, but does not bother with the group 2 services.

[00182] The method can involve the mechanic providing the verification of the engine repairs to the vehicle maintenance tracker while the vehicle maintenance tracker automatically generates both (1) vehicle repair information prioritized by importance of services needed to operate the vehicle and (2) a schedule for vehicle service prioritized by importance of services needed to operate the vehicle showing, such as in this example that the engine starter requires 2 days of service, the engine alternator requires 1 day of service, and the engine mounts require 1 week for service.

[00183] Turning now to the apparatus for conditional, proximity-based authorization for the use of equipment by a user, it is submitted that specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis of the claims and as a representative basis for teaching persons having ordinary skill in the art to variously employ the present invention. [00184] Key device as used herein can refer to any device capable of communicating electronically with a piece of equipment or machinery. Exemplary devices include, but are not limited to: cellular phones, laptop computers, tablet computers, portable media devices, wearable devices, implanted devices, and the like.

[00185] An operable apparatus, equipment, or machinery as used herein can refer to any device operable by a user, wherein it is desirable to restrict access to the device for safety or business reasons. Exemplary devices include, but are not limited to: industrial equipment, vehicles, electronic equipment, entry doors, safes, airplanes, forklifts, cranes, robots, drones, and the like.

[00186] The present invention comprises a key device for communicating with at least one apparatus operable by a user, wherein the at least one apparatus must be enabled for use. The apparatus can range from personally carried devices, such as cellular phones, to large pieces of machinery, such as construction equipment or vehicles.

[00187] Key devices currently in use can verify identity, or determine that the key corresponds to an apparatus in order to provide access to the apparatus. [00188] The present invention discloses a key device which comprises not only a verification means that the key corresponds to an apparatus as described above but, in various embodiments, further comprises a positional identification mechanism for identifying a location of the key device, at least one prerequisite condition which must be fulfilled in order for the key device to enable operation of the apparatus, and a means of communication with the apparatus.

[00189] The key device can comprise a positional identification mechanism which determines a location of the key device. The location of the key device can further conditionally control operation of an apparatus as discussed more in detail below. The position of the key device can be determined as an absolute position, such as by the use of a global positioning system (GPS). [00190] Alternatively, the position of the key device can be determined as a relative position in relation to some significant structure. For example, a vehicle key can determined to be within the vehicle, or external to the vehicle. Various means of determining such positions are known to persons having ordinary skill in the art. Determinations can be made using technology such as near field communications, magnetic sensors, radio emitting sensors, or any similar means.

[00191] The key device can also contain one or more prerequisite conditions which must be fulfilled in order to enable operation of an apparatus. Such a prerequisite condition can be incorporated in the key device via hard coding into the key device components, or implemented by using software to allow for rapid and easy customization of the prerequisite condition.

[00192] Prerequisite conditions can be dynamic and implemented from a remote location and transmitted to the key device.

[00193] The key device can comprise a computer to enable the storage of the prerequisite conditions. The key device can comprise a key device processor, a non- transitory key device storage, a means of transmitting data, a means of receiving data, and a power source, all in electronic communication with each other. Persons having ordinary skill in the art will be well aware of various structures accomplishing the above purposes.

[00194] The key device can store the prerequisite conditions locally on the key device storage, or communicated to the key device via a network such as the internet, peer to peer networks, satellite communication, a line of sight network, and the like. In embodiments, a remote computer can determine and transmit conditions to multiple key devices. Conditions can be determined based upon rules, or input manually by, for example, supervisory personnel.

[00195] It is important to note that the prerequisite condition can be a positive or a negative condition. An exemplary positive condition can be that the key device is inside a vehicle. An exemplary negative condition can be that the user of an apparatus has not been consuming alcohol, or even that the key device is not in the vehicle.

[00196] Various exemplary conditions that a user may need to meet in order to operate an apparatus include, but are not limited to: the key device is in a predetermined location, the key device is not in a predetermined location, a user of an apparatus has not completed a pre-usage inspection, a user of an apparatus has not walked in a pre- defined pattern prior to operation of an apparatus, a specific software is in operation on the key device, the apparatus has fuel or power below a certain level, apparatus is unsafe to operate, the apparatus is in need of repair, apparatus has been identified as having a defect, user is not authorized to operate the apparatus, user has not completed appropriate training, and the like.

[00197] Other conditions may include business specific conditions, such as an inspection report or logbook not being signed, the apparatus not having been serviced or inspected, an apparatus not in the proper location, a malfunction of the apparatus or key device, improper user identification through biometrics or behavior, health or physical condition of the user, driving at specific times of day or night, authorization level of the user, safety precautions not in place, preventive maintenance being due, low grease or oil level, increased potential for theft, and the like.

[00198] The prerequisite conditions can themselves be conditional, and comprise one or more sub-conditions. The sub-conditions can alter the actual prerequisite condition based upon various factors, such as environmental considerations, safety considerations, geographical considerations, and other similar considerations.

[00199] The key device can be in communication with one or more sensors, which may provide data upon which the prerequisite conditions or the sub-conditions may be contingent. The sensors can be any sensors that provide pertinent information. For example, an accelerometer in communication with the key device can determine that an accident has occurred due to the sudden deceleration of an apparatus. This in turn may create a prerequisite condition that a certain step or series of steps must be undertaken before the apparatus is enabled for operation. [00200] In another example, a health monitoring device may be placed upon the user that does not allow for an apparatus to be operated by a user in poor health, i.e., the user has not had enough sleep or has a heart condition. [00201] Numerous sensors exist known to persons having ordinary skill in the art for selection which can then be logically combined or linked to prerequisite conditions or sub- conditions customizable for a variety of safety, cost, environmental, business, or other goals. [00202] The key device can determine a status of the at least one prerequisite condition and, through communication with the apparatus, can enable operation of at least one function of the at least one apparatus by the user if the key device is in a desired location and the at least one prerequisite condition has been fulfilled. [00203] Alternatively, the key device can determine a status of the at least one prerequisite condition and, through communication with the at least one apparatus, actively disable operation of at least one function of the at least one apparatus by the user if the key device is not in the desired location or the at least one prerequisite condition has not been fulfilled,

[00204] The following narratives provide exemplary uses of the device.

[00205] In one embodiment of the invention, the key device can be used by consumers for personal use. An exemplary use would be for a parent to prevent children from texting while driving a vehicle to ensure a safer environment for the child.

[00206] In this embodiment, the key device can be a worn item such as a wristband or a watch, a carried item such as a cellular phone or a personal tablet computer, or various combinations thereof.

[00207] The key device can comprise one or more prerequisite conditions, customizable by the parent or other authorized individual. In this embodiment, the prerequisite conditions can include elements such as determining whether the key device is within the vehicle, whether the key device is within the driver's seat, whether the vehicle is in motion, and the like. [00208] The prerequisite conditions can themselves be conditional upon sub-conditions. For example, the conditions may vary based upon the user of the key device, the apparatus being controlled, the age of a child, and the like.

[00209] The key device can be in electronic communication with any apparatus capable of sending or receiving text messages. A parent can configure the key device to actively disable text messaging capability if, for example, the key device is within a vehicle which is moving at a rate greater than 3 miles per hour. A parent can allow for voice activated commands only when the vehicle is in motion. However, if rain is detected, then all or selected voice activated commands can be actively disabled if the key device is within a vehicle.

[00210] Determination of the location of the key device can be accomplished by various sensors transmitting information to the key device, such as via magnetic or radio waves, near field communication chips, a cradle or mounting within which the key device must be placed, and the like.

[00211] Alternative embodiments may also have the key device not allow a vehicle to be placed into "drive" or "reverse" when the user is actively texting or speaking on a phone. The key device can monitor the status of the prerequisite conditions, and enable or disable functions on the at least one apparatus as desired.

[00212] In another embodiment, the key device can be configured for commercial use. [00213] A typical example might be a business with a fleet of vehicles, or a number of employees operating commercial equipment. [00214] The key device in this instance can be a personal mobile device such as a cellular phone or a tablet pc. In other embodiments, the key device can be a wearable device, such as an electronic bracelet, a watch, an identification card worn on a lanyard, and the like.

[00215] In embodiments, the key device may be required to be placed within a mounting or cradle in order to make the vehicle or commercial equipment operational. In other embodiments, the location of the key device can be ascertained with various known mechanisms, such as magnetic or radio waves, near field communication chips, GPS, wireless network triangulation, and the like.

[00216] The key device can identify the user of the apparatus (vehicle or commercial equipment). In various embodiments, the identification can be as simple as a pin code that is input by the user. For more sensitive apparatus, the identification of the user can be more precise, and make use of various sensors or software to implement biometric identification such as facial recognition, fingerprint, retinal scans, voice recognition, and the like. It is contemplated that behavioral analysis can be implemented to aid in or be the primary means of identifying a user. [00217] The key device can then identify the apparatus. The apparatus may be a specific piece of machinery, such as a lathe, power tool, a bulldozer, a backhoe, etc. In embodiments, the apparatus can be a specific vehicle in a fleet of vehicles.

[00218] The key device can be configured to control various apparatus. For example, in the instance of a commercial truck driver, the key device can enable or disable placing the vehicle into gear, while simultaneously enabling or disabling a phone from sending and receiving text messages.

[00219] A number of established and variable prerequisite conditions can be incorporated into the key device. The conditions may be resident upon the key device, or received by the key device through a transmission or synchronization process. [00220] Prerequisite conditions may be contingent upon subconditions, and alter the behavior of the key device based upon various factors. Exemplary conditions and sub conditions include: [00221] The specific user of the key device. The key device may operate differently based upon the user of the key device. Factors specific to the user such as training, licensure, alertness, certifications, level of authorization, hours of continuous service, health, experience, tenure, level of security clearance, and the like can all affect whether the prerequisite condition is met, or even dictate what the prerequisite condition is.

[00222] The specific apparatus. As discussed above, a single key device can be used to enable or disable a number of apparatus. The specific piece of machinery, equipment, vehicle, aircraft, door, and the like can all affect whether the prerequisite condition is met, or dictate what the prerequisite condition is.

[00223] Environmental conditions. Elements such as geography, terrain, traffic, weather, time of day, level of radiation, chemical presence, electromagnetic pulse, contamination, and the like can all affect whether the prerequisite condition is met, or dictate what the prerequisite condition is.

[00224] Business considerations. Considerations such as the specific client for which work is performed, regulatory rules, local laws, insurance requirements, profit, and the like can all affect whether the prerequisite condition is met, or dictate what the prerequisite condition is.

[00225] Safety conditions. Considerations such as whether the apparatus has been properly inspected, whether insurance requirements are met, the current apparatus usage habits of the user, road hazards that have been reported or detected, the repair needs and history of the apparatus, wear and tear, presence of a recall notice, and the like can all affect whether the prerequisite condition is met, or dictate what the prerequisite condition is. [00226] The above exemplary but non-limiting list of prerequisite conditions, in combination with a required proximity of the key device can be used to enable or disable certain functions of the apparatus. [00227] For example, a commercial truck driver may not be allowed to put the vehicle into gear without completing a pre-trip inspection, if his license has expired, if the truck has a mechanical defect, etc. The operator of a bulldozer may not be allowed to start the vehicle if he is inputting data on his phone. [00228] The key device can keep records of location, user inputs, and prerequisite conditions for reporting purposes at a later time.

[00229] Turning now to the Figure, the Figure is a block diagram illustrating the components of the device for conditional, proximity- based equipment use authorization.

[00230] The device for conditional, proximity- based equipment use authorization 900 can comprise an apparatus 902, a mounting 906, and a key device, 1000.

[00231] The apparatus 902, as discussed above, can be any apparatus that must be enabled for use by a user. Exemplary apparatus can range from personally carried devices, such as cellular phones, to large pieces of machinery, such as construction equipment or vehicles. In embodiments, the apparatus can comprise a motor 904.

[00232] In embodiments, the device 900 can comprise a mounting 906, wherein the mounting can constrain the motion of a key device 1000. The mounting 906 can be a structure that selectively clasps the key such as a cradle for a phone or other similar structure. In embodiments, the mounting 906 can electronically communicate with the apparatus 902. [00233] The device 900 can further comprise a key device 1000. The key device can comprise a key device processor 1002, a means of transmitting data 1004, a means of receiving data 1006, and a power source 1008 all in electronic communication with each other.

[00234] The key device processor 1002 can be any microprocessor used in computing devices or portable devices.

[00235] In embodiments the means of transmitting data 1004 and the means of receiving data 1006 can make use of any means known to persons having ordinary skill in the art for the transfer of data. Exemplary methods include, but are not limited to: physical channels such as wires, electromagnetic signals such as radio waves, line of sight signals, electrical signals, microwave signals, Bluetooth signals, WiFi signals, and the like.

[00236] The power source 1008 can supply power to the key device 1000 and its various components. In embodiments, the power source can be shared with or charged by the apparatus or a power source within the apparatus.

[00237] In embodiments, the key device 1000 can be in communication with a remote computer 1012 through a network 1010. The remote computer can communicate with the key device through the means of transmitting data 1004 and the means of receiving data 1006.

[00238] The key device 1000 can comprise a biometric identification device 1014. Exemplary devices can include voice recognition devices, retinal scanners, fingerprint scanners, facial recognition cameras, and the like.

[00239] In embodiments, the key device 1000 can be in communication with a camera 1016. The key device can also be in communication with one or more sensors 1020, such as an accelerometer, a heart rate monitor, a health monitoring device, an optical character recognition device, a computer such as a vehicle computer, gyrometer, global positioning sensor, odometer, speedometer, pedometer, breathalyzer, biometer, device to measure behavioral traits, and the like. Other sensors can include sensors for rain, temperature, tire pressure or tread wear, water level, or even data from internet databases (such as health care network data). Persons having ordinary skill in the art can determine sensors or data needed for specific applications.

[00240] The key device can comprise or be in electronic communication with a positional identification mechanism 1018 to determine the position of the key device. The positional identification mechanism 1018 can be a global positioning system, a fixed mounting whose location is known, or various magnetic, radio, near field communication mechanisms, and the like. [00241] The key device can also comprise a non-transitory key device data storage 1060. The data storage 1060 can comprise a nonvolatile data storage medium for storage of information, computer instructions and the like.

[00242] In embodiments, the data storage 1060 can comprise a prerequisite condition 1062, a first record 1066 of all user inputs, a second record 1068 of the locations of the key device for a predetermined time, and a plurality of computer instructions 1070.

[00243] The plurality of computer instructions 1070 can include instruction 1072 instructing the key device processor 1002 to determine the location of the key device.

[00244] The plurality of computer instructions 1070 can include instruction 1074 instructing the key device processor 1002 to determine the status of the at least one prerequisite condition. [00245] The plurality of computer instructions 1070 can include instruction 1076 instructing the key device processor 1002 to communicate with at least one apparatus 902.

[00246] The plurality of computer instructions 1070 can include instruction 1078 instructing the key device processor 1002 to enable or disable at least one apparatus 902.

[00247] In embodiments, the data storage 1060 can comprise a module 1064 for identifying a user based upon behavioral patterns. Behavioral patterns can include physical traits such as stride length, manner of sitting, manner of standing, and the like. In embodiments, behavioral patterns can include learned behaviors or habits, such as a consistent order in which tasks are accomplished, a manner of completing a task, a manner of beginning a task, and the like.

[00248] In embodiments, the plurality of computer instructions 1070 can include instruction 1080 instructing the key device processor 1002 to generate reports from the first record 1066 of all user inputs, and/or the second record 1068 of the locations of the key device. Reports can comprise charts, graphs, and the like. A remote computer 1012 can aggregate data for comparison to collected data, established standards and norms, or other benchmark data.

[00249] In embodiments, the plurality of computer instructions 1070 can include instruction 1082 instructing the key device processor 1002 to display feedback to the user or send feedback to a remote computer 1012.

[00250] Turning now to methods and systems for automated asset inspection, service, and maintenance, it is noted that specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis of the claims and as a representative basis for teaching persons having ordinary skill in the art to variously employ the present invention.

[00251] The methods and systems for automated asset inspection, service, and maintenance are able to manage and track assets based upon business, regulatory, or other requirements. While it is contemplated that the invention is applicable to numerous industrial scenarios, exemplary descriptions will concentrate upon its application to a fleet of vehicles or similarly mobile assets.

[00252] The system comprises at least one client device in communication with a mobile asset management module. The client device can have a client processor, a client data storage, a client data transmitter, a client data receiver, and at least one sensor for detecting asset status information. [00253] The client processor can be any electronic circuitry such as a processor or a microprocessor capable of carrying out the instructions of a computer program. The client data storage can be any computer readable medium capable of storing data in a non- transitory fashion. The data storage excludes any transitory signals but can include any non- transitory data storage circuitry, such as buffers, cache, and queues, within transceivers of transitory signals.

[00254] The client device can also have a client data transmitter and a client data receiver. In embodiments, the data transmitter and the data receiver can be a single device. The transmitter may communicate through a physical connection, or wirelessly such as by the use of radio waves, infrared communication, line of sight transmission, and the like.

[00255] The client device can also have at least one sensor for detecting information about an asset status. Exemplary client device sensors include, but are not limited to: a pedometer, a global positioning system sensor, a radio frequency receiver or transmitter, an infrared scanner, an internet receiver or transmitter, a camera, an accelerometer, an environmental sensor, a radar receiver or transmitter, a proximity sensor, a timer, a motion detector, and the like. [00256] The client device can also have a plurality of computer instructions stored within the client data storage. These computer instructions can instruct the client processor to receive an input from a user, determine authorized actions for the user, receive data, and transmit data. [00257] Input from a user can be in multiple forms, such as physical inputs such as typing, handwriting, motions of the client device, voice commands, and the like.

[00258] The client device can receive data from and transmit data to a mobile asset management module. The client device can also communicate with other systems as warranted by the specific application. [00259] The mobile asset management module can be in communication with the client device. The mobile asset management module can have a module processor, a module data storage, a module data transmitter, and a module data receiver. [00260] The module processor can be any electronic circuitry such as a processor or a microprocessor capable of carrying out the instructions of a computer program. The module data storage can be any computer readable medium capable of storing data in a non- transitory fashion. The data storage excludes any transitory signals but can include any non-transitory data storage circuitry, such as buffers, cache, and queues, within transceivers of transitory signals.

[00261] The mobile asset management module can also have a module data transmitter and a module data receiver. In embodiments, the data transmitter and the data receiver can be a single device. The transmitter may communicate through a physical connection, or wirelessly such as by the use of radio waves, infrared communication, line of sight transmission, and the like.

[00262] The mobile asset management module can also have a plurality of computer instructions stored within the module data storage. These computer instructions can instruct the module processor to determine an identity of the asset, receive asset status information from the at least one client device, analyze asset status information from the at least one client device to form analyzed data, determine a status of the asset based upon the analyzed data, determine a service requirement of the asset based upon the analyzed data, and transmit the service requirement of the asset.

[00263] In embodiments, the mobile asset management module can have computer instructions instructing the module processor to display a procedure to the user, collect the asset status information based upon the procedure, log asset status information to form logged data, change the status of the asset based upon the service requirement of the asset, generate a work order based upon the service requirement of the asset and transmit the work order to the at least one client device, display or transmit the steps of a vehicle inspection or an equipment inspection, verify that the steps of the vehicle inspection or the equipment inspection are properly conducted by the user, determine an amount of time taken by the user to conduct the steps of the vehicle inspection or the equipment inspection, determine a distance traveled by the user to conduct the steps of the vehicle inspection or the equipment inspection, or respond to a triggering event. [00264] The mobile asset management module can also communicate with the client device to determine a service requirement and optimized service timing and location for the asset. For example, a truck running low on fuel can be notified that a gas station with discounts for the specific trucking company is on route and accessible to the truck in one hour and another accessible in two hours. The mobile asset management module can determine the least disruptive service time and location based upon business rules. Various configurable rules can be used for this determination, such as distance until empty, discounts on fuel, smart-routing, hours of service for a driver, traffic patterns, and the like.

[00265] In embodiments, the triggering event can be an accident or an injury. For example, the client device can determine and communicate to the mobile asset management module that an accident has occurred. This can be because of information received from a sensor in communication with the client device, a sensor which is part of the client device, or a user input. [00266] When an accident or a triggering event is detected, the mobile asset management module can determine if a drug or alcohol test is required. The requirement may be based upon business or regulatory needs, and the mobile asset management module can have access to a group of user configurable rules, or regulatory information. It can then determine the best location to send the driver or other worker, schedule the appointment, provide directions, confirm arrival, notify a concerned party and allow the driver or other worker to input results, receipts, confirmation or simply notify a concerned party upon completion or at any time before or after the testing has occurred.

[00267] The mobile asset management module can be configured to respond in a number of ways to a triggering event. Sensor information or a user input can be used to determine the identity and/or severity of a triggering event. The mobile asset management module can then specify a procedure based upon the identity and/or severity of a triggering event. For example, the mobile asset management module can provide instructions to a user for a procedure to be followed in the event of an accident. The procedure can include creating a report and notifying interested parties of the triggering event.

[00268] An exemplary use of the present embodiments with respect to a fleet of trucks is presented below to aid in understanding the invention. The invention is not intended to be limited to the following application.

[00269] A system for automated inspection and maintenance of an asset can be implemented to manage assets such as a fleet of trucks delivering cargo. The cargo can be delivered as a trailer attached to a tractor, or as various discrete shipments within a truck.

[00270] The system can have at least one client device comprising a client processor, a client data storage, a client data transmitter, a client data receiver, and a plurality of computer instructions stored within the client data storage instructing the client processor to receive an input from a user, determine authorized actions for the user, receive data, and transmit data.

[00271] The user can be a driver of a truck, a person who repairs or maintains the truck, a manager of the fleet of trucks, or any person requiring detailed and real time information about the trucks. In embodiments, a cellular phone or personal digital assistant can provide the necessary hardware for acting as a client device. Other devices specific to an application can also be implemented by persons having ordinary skill in the art.

[00272] The client device can have a number of login procedures specific to various users. These procedures are well known to persons having ordinary skill in the art and need not be detailed herein. The client device can determine which user is presently providing input to the client device, and determine the authorized actions of the user.

[00273] For example, the client device may determine that a specific driver is not certified to drive the vehicle in question, and present a warning message that the driver is not authorized to operate the vehicle. The client device can also receive and transmit data, such as to the mobile asset management module discussed below. [00274] The client device can receive input from the user, such as a driver or mechanic, be in communication with one or more sensors, or even comprise sensors for determining the truck status. [00275] In embodiments, the client device can be used by a driver, can act as an inspection device, a service device, a mechanic device, and the like.

[00276] The system can have a mobile asset management module in communication with the one client device. The mobile asset management module can be a centralized computer in communication with the client device, or in other embodiments be attached to or stored within the client device.

[00277] Any device capable of performing the functions of a computer can be used as the mobile asset management module. The mobile asset management module comprises a module processor, a module data storage, a module data transmitter, and a module data receiver. In embodiments the module processor may be the same structure or device as the client processor.

[00278] The mobile asset management module can have a plurality of computer instructions stored within the module data storage, wherein the plurality of computer instructions comprises computer instructions instructing the module processor to determine an identity of the asset, receive asset status information from the at least one client device, analyze asset status information from the at least one client device to form analyzed data, determine a status of the asset based upon the analyzed data, determine a service requirement of the asset based upon the analyzed data, and transmit the service requirement of the asset.

[00279] Within the present example, the mobile asset management module can identify a specific truck from a fleet of trucks. Once the asset's identity has been determined, the mobile asset management module can receive a variety of asset status information from the client device. [00280] Depending on the business needs of the specific application, the asset information may be user input, or received from one or more sensors either in communication with, or attached to the client device. Exemplary sensors include, but are not limited to: a pedometer, a global positioning system sensor, a radio frequency receiver or transmitter, an infrared scanner, an internet receiver or transmitter, a camera, an accelerometer, an environmental sensor, a radar receiver or transmitter, a proximity sensor, a timer, a motion detector, a pressure switch, a gyrometer, a radiation sensor, a chemical sensor, a carbon monoxide sensor, an oxygen sensor, an altimeter, a button, a touch pad, or a barometer. [00281] For example, the mobile asset management module may receive information that the specific truck in question has a fuel tank that is twenty percent full. Using business logic that is configurable, the mobile asset management module can determine whether the fuel is sufficient for the route that the truck will take. If not, the mobile asset management module can determine the best place for the truck to be refueled based upon distance from route, traffic conditions, discounts offered by fuel stations, or any other pertinent logic.

[00282] The mobile asset management module can also determine a procedure or set of procedures that need to be followed for the truck. These procedures may be user specific, vehicle (or asset) specific, business specific, due to regulatory considerations, insurance requirements, and the like.

[00283] Upon determination of the procedure, the mobile asset management module can display the procedure to the user, and require the user to verify or attest that the procedure has been followed. The mobile asset management module can also be in communication with the client device and/or sensors to verify that the procedure has been followed.

[00284] For example, the truck may require a pre-trip inspection prior to being driven. The mobile asset management module can determine that this is the case and display to the driver a set of instructions or a procedure for a pre-trip inspection. The mobile asset management module can require the driver to input the result of each inspection step. [00285] In embodiments, the mobile asset management module can be in communication with the client device to receive sensor information, such as determining a distance traveled by the driver to see if it meets a minimum required distance to walk around the vehicle. [00286] Other similar checks, such as using object recognition, pictures of inspected items, global positioning systems, time to complete procedures, or other sensors as described within this document can be used by the mobile asset management module to independently verify that procedures have been followed. [00287] The mobile asset management module can use asset status information, either as provided by a user, or as gathered from a sensor to determine a status of the asset. Based upon asset status information received, the mobile asset management module can change the status of the asset. For example, the mobile asset management module may determine that the truck is not drivable because it needs repairs, requires certifications or other actions to comply with regulatory requirements, is not authorized for the user to drive, and the like.

[00288] The mobile asset management module can further determine necessary actions to be taken and generate and transmit work orders for repairs, service, and the like to a client device or other location. For example, if a pre-trip inspection turns up a defective part, the mobile asset management module can determine the necessary repairs, determine the best place or mechanic for conducting the repairs, and transmit a directive to the driver to deliver the vehicle to the mechanic, and transmit a work order to the mechanic authorizing the proper repairs. [00289] In embodiments, the mobile asset management module may display procedures or information on the client device based upon a triggering event. The triggering event can be anything that the mobile asset management module receives information about. For example, accelerometer readings from the client device can indicate to the mobile asset management module that an accident has occurred. The mobile asset management module can then display an asset specific procedure to be followed in the event of an accident. [00290] Items such as required documentation, witness statements, pictures, narratives, and the like can be received from the client device and logged by the mobile asset management module. In embodiments, the mobile asset management module can further transmit the information to regulatory agencies, insurance agencies, management, and the like. In embodiments, the mobile asset management module can further determine whether company policies or local regulations require a drug test and display instructions on where to complete such actions to the driver by determining the nearest available facility.

[00291] In some instances, tractor trailers may change trailers as well as load and offload cargo. In these instances, the mobile asset management module can track the tractor and the trailer independently of one another. In embodiments, the cargo can be an asset that is managed by the mobile asset management module.

[00292] The present invention allows for the management and tracking of various assets, especially when multiple assets are mobile and have multiple users/operators.

[00293] While these embodiments have been described with emphasis on the embodiments, it should be understood that within the scope of the appended claims, the embodiments might be practiced other than as specifically described herein.