IPC분류정보
국가/구분 |
United States(US) Patent
등록
|
국제특허분류(IPC7판) |
|
출원번호 |
US-0556140
(2009-09-09)
|
등록번호 |
US-8416067
(2013-04-09)
|
발명자
/ 주소 |
- Davidson, Mark J.
- Olsen, III, John A.
|
출원인 / 주소 |
- United Parcel Service of America, Inc.
|
대리인 / 주소 |
|
인용정보 |
피인용 횟수 :
54 인용 특허 :
253 |
초록
▼
According to various embodiments, a fleet management system is provided for capturing, storing, and analyzing telematics data to improve fleet management operations. The fleet management system may be used, for example, by a shipping entity (e.g., a common carrier) to capture telematics data from a
According to various embodiments, a fleet management system is provided for capturing, storing, and analyzing telematics data to improve fleet management operations. The fleet management system may be used, for example, by a shipping entity (e.g., a common carrier) to capture telematics data from a plurality of vehicle sensors located on various delivery vehicles and to analyze the captured telematics data. In particular, various embodiments of the fleet management system are configured to analyze engine idle data in relation to other telematics data in order to identify inefficiencies, safety hazards, and theft hazards in a driver's delivery process. The fleet management system may also be configured to assess various aspects of vehicle performance, such as vehicle travel delays and vehicle speeds. These analytical capabilities allow the fleet management system to assist fleet managing entities, or other entities, in analyzing driver performance, reducing fuel and maintenance costs, and improving route planning.
대표청구항
▼
1. A fleet management computer system comprising: one or more memory storage areas; andone or more processors;wherein said one or more processors are, collectively, configured to: (i) receive telematics data from one or more vehicle sensors associated with a vehicle, said telematics data comprising
1. A fleet management computer system comprising: one or more memory storage areas; andone or more processors;wherein said one or more processors are, collectively, configured to: (i) receive telematics data from one or more vehicle sensors associated with a vehicle, said telematics data comprising engine idle data relating to the engine idle time of said vehicle;(ii) associate said telematics data with a particular segment of a vehicle trip; and(iii) execute a step selected from a group consisting of: (a) determining whether said telematics data indicates a potential inefficient operation by a driver of said vehicle and, in response to determining that said telematics data indicates a potential inefficient operation by said driver, generating an alert indicating said potential inefficient operation;(b) determining whether said telematics data indicates a potential safety hazard created by a driver of said vehicle and, in response to determining that said telematics data indicates a potential safety hazard created by said driver, generating an alert indicating said potential safety hazard; and(c) determining whether said telematics data indicates a potential theft hazard created by a driver of said vehicle and, in response to determining that said telematics data indicates a potential theft hazard created by said driver, generating an alert indicating said potential theft hazard. 2. The fleet management computer system of claim 1, wherein: said computer system further comprises a user interface; andsaid step of generating an alert indicating a potential inefficient operation comprises displaying via said user interface data indicating said potential inefficient operation. 3. The fleet management computer system of claim 2, wherein said particular segment is selected from a group consisting of: a start of trip segment;a during travel segment; andan end of trip segment. 4. The fleet management computer system of claim 1, wherein: said computer system further comprises a user interface; andsaid step of generating an alert indicating a potential safety hazard comprises displaying via said user interface data indicating said potential safety hazard. 5. The fleet management computer system of claim 1, wherein: said computer system further comprises a user interface; andsaid step of generating an alert indicating a potential theft hazard comprises displaying via said user interface data indicating said potential theft hazard. 6. The fleet management computer system of claim 1, wherein: said telematics data further comprises seat belt data indicating the status of a seat belt in said vehicle; andsaid step (a) comprises determining, based on said telematics data, whether a driver of said vehicle fastened or unfastened a driver's side seat belt of said vehicle while said vehicle's engine was idling. 7. The fleet management computer system of claim 1, wherein: said telematics data further comprises seat belt data indicating the status of a seat belt in said vehicle; andsaid step (b) comprises determining, based on said telematics data, whether a driver of said vehicle fastened or unfastened a driver's side seat belt of said vehicle while said vehicle was moving. 8. The fleet management computer system of claim 1, wherein: said telematics data further comprises door data indicating the status of a door of said vehicle; andsaid step (a) comprises determining, based on said telematics data, whether said door was opened or closed while said vehicle was idling. 9. The fleet management computer system of claim 1, wherein: said telematics data further comprises door data indicating the status of a door of said vehicle; andsaid step (c) comprises determining, based on said telematics data, whether said door was opened or closed while said vehicle was idling. 10. The fleet management computer system of claim 1, wherein: said engine idle data comprises data indicating engine idle events that define engine idle segments; andsaid step (a) comprises identifying, based on said telematics data, engine idle segments caused by travel delays. 11. The fleet management computer system of claim 10, wherein: said step (a) further comprises: determining, based on said identified engine idle segments caused by travel delays, an amount of engine idle time caused by travel delays for said vehicle for a particular portion of said vehicle trip; anddetermining, based on said telematics data and said amount of engine idle time caused by travel delays, the corrected speed of said vehicle for said particular portion of said vehicle trip. 12. The fleet management computer system of claim 11, wherein said corrected speed is an average speed of said vehicle during said particular portion of said vehicle trip less travel delays. 13. The fleet management computer system of claim 10, wherein: said step (a) further comprises: determining, based on said telematics data, the total amount of engine idle time for said vehicle during a particular portion of said vehicle trip;determining, based on said engine idle segments caused by travel delays, an amount of engine idle time caused by travel delays for said vehicle during said particular portion of said vehicle trip; anddetermining, based on said total amount of engine idle time and said amount of engine idle time caused by travel delays, a corrected amount of engine idle time for said vehicle during said particular portion of said vehicle trip, wherein said corrected amount of engine idle time is the total amount of engine idle time for said vehicle during said particular portion of said vehicle trip exclusive of engine idle time caused by travel delays. 14. The fleet management computer system of claim 13, wherein: said step (a) further comprises: determining a target amount of engine idle time for a vehicle operated within said particular portion of said vehicle trip; andcomparing said target amount of engine idle time to said corrected amount of engine idle time. 15. The fleet management computer system of claim 10, wherein: said step (a) further comprises: determining, based on said telematics data, a total amount of engine running time for said vehicle during a particular portion of said vehicle trip;determining, based on said engine idle segments caused by travel delays, an amount of engine idle time caused by travel delays for said vehicle during said particular portion of said vehicle trip; anddetermining, based on said total amount of engine running time and said engine idle time caused by travel delays, a corrected engine idle time percentage for said vehicle during said particular portion of said vehicle trip, wherein said corrected engine idle time percentage is the percentage of engine running time during said portion of said vehicle trip that said vehicle's engine was idling exclusive of engine idle time caused by travel delays. 16. The fleet management computer system of claim 15, wherein: said step (a) further comprises: determining a target engine idle time percentage for a vehicle operated within said particular portion of said vehicle trip; andcomparing said target engine idle time percentage to said corrected engine idle time percentage. 17. The fleet management computer system of claim 1, wherein: said step (a) comprises: determining, based on said telematics data, the speed of said vehicle for a particular portion of said vehicle trip. 18. The fleet management computer system of claim 17, wherein: said step (a) further comprises: determining a target speed for a vehicle for a particular portion of said vehicle trip; andcomparing said target speed to said speed of said vehicle. 19. The fleet management computer system of claim 1, wherein: said step (a) comprises: determining, based on said telematics data, a total amount of engine idle time for said vehicle during a particular portion of said vehicle trip; wherein said particular portion of said vehicle trip comprises: the entire vehicle trip;a portion of said vehicle trip occurring during one of said particular segments of said vehicle trip;a portion of said vehicle trip occurring within a geofenced area;a portion of said vehicle trip occurring between two geographic points; ora portion of said vehicle trip occurring during a particular time period. 20. The fleet management computer system of claim 19, wherein: said step (a) further comprises: determining a target amount of engine idle time for a vehicle for said particular portion of said vehicle trip; andcomparing said target amount of engine idle time to said total amount of engine idle time. 21. The fleet management computer system of claim 1, wherein: said step (a) comprises: determining, based on said telematics data, the engine idle time percentage for said vehicle during a particular portion of said vehicle trip; wherein: said engine idle time percentage is the percentage of engine running time during which the engine of said vehicle is idling. 22. The fleet management computer system of claim 21, wherein: said step (a) further comprises: determining a target engine idle time percentage for a vehicle for said particular portion of said vehicle trip; andcomparing said target engine idle time percentage to said engine idle time percentage. 23. The fleet management computer system of claim 1, wherein: said one or more vehicle sensors comprise a non-idle time sensor;said telematics data is first telematics data;said one or more processors are further configured to receive second telematics data from said non-idle time sensor; andthe step of determining whether said telematics data indicates a potential inefficient operation is based on said first and second telematics data. 24. The fleet management computer system of claim 23, wherein said second telematics data is selected from the group consisting of: seat belt data; vehicle door data; vehicle handle data; engine ignition data; engine speed data; vehicle speed data; vehicle heading data; vehicle backing data; vehicle location data; distance traveled data; portable acquisition device data; throttle position data; brake pedal position data; parking brake position data; engine oil pressure data; engine temperature data; and engine fault data. 25. The fleet management computer system of claim 1, wherein said one or more processors are, collectively, configured to execute the step (a) of determining whether said telematics data indicates a potential inefficient operation by said driver of said vehicle and, in response to determining that said telematics data indicates a potential inefficient operation by said driver, generating an alert indicating said potential inefficient operation. 26. The fleet management computer system of claim 1, wherein said one or more processors are, collectively, configured to execute the step (b) of determining whether said telematics data indicates a potential safety hazard created by said driver of said vehicle and, in response to determining that said telematics data indicates a potential safety hazard created by said driver, generating an alert indicating said potential safety hazard. 27. The fleet management computer system of claim 1, wherein said one or more processors are, collectively, configured to execute the step (c) of determining whether said telematics data indicates a potential theft hazard created by a driver of said vehicle and, in response to determining that said telematics data indicates a potential theft hazard created by said driver, generating an alert indicating said potential theft hazard. 28. A fleet management system comprising: (a) a plurality of fleet vehicles, each including: one or more vehicle sensors; andat least one telematics device;(b) at least one computer network;(c) one or more central servers; and(d) a user interface;wherein said telematics device of each of said fleet vehicles is configured to: receive telematics data from one or more of said vehicle sensors of an associated fleet vehicle, wherein said telematics data comprises data relating to the engine idle time of said associated fleet vehicle;associate said telematics data with contextual data; andtransmit said telematics data over said network to one or more of said central servers; andwherein said one or more central servers are configured to: (i) receive said telematics data from said telematics device of each of said fleet vehicles;(ii) execute the step of associating said telematics data with a particular segment of a vehicle trip; and(iii) execute a step of: determining whether said telematics data indicates a potential inefficient operation by one or more drivers of one or more of said fleet vehicles and, in response to determining that said telematics data indicates a potential inefficient operation by said one or more drivers, displaying via said user interface data indicating said potential inefficient operation;determining whether said telematics data indicates a potential safety hazard created by one or more drivers of one or more of said fleet vehicles, and, in response to determining that said telematics data indicates a potential safety hazard created by said one or more drivers, displaying via said user interface data indicating said potential safety hazard; ordetermining whether said telematics data indicates a potential theft hazard created by one or more drivers of one or more of said fleet vehicles, and, in response to determining that said telematics data indicates a potential theft hazard created by said one or more drivers, displaying via said user interface data indicating said potential theft hazard. 29. The fleet management system of claim 28, further comprising: (e) one or more portable data acquisition devices;wherein said telematics device of each of said fleet vehicles is further configured to transmit said telematics data over said network to said one or more portable data acquisition devices;wherein said one or more portable data acquisition devices are configured to: receive said telematics data; andtransmit said telematics data over said network to at least one of said one or more central servers; andwherein said one or more central servers are further configured to receive telematics data. 30. The fleet management system of claim 28, wherein said particular segment is selected from a group consisting of: a start of trip segment;a during travel segment; andan end of trip segment. 31. A fleet management computer system comprising: one or more memory storage areas; andone or more processors;wherein said one or more processors are, collectively, configured to: (i) receive telematics data from one or more vehicle sensors associated with a vehicle, wherein said telematics data comprises engine idle data relating to the engine idle time of said vehicle; and(ii) associate one or more portions of said telematics data with one or more vehicle trip segments by identifying engine idle segments indicated by said engine idle data and associating each of said engine idle segments with a particular one of said vehicle trip segments, wherein said one or more vehicle trip segments comprise: a start of trip segment representing a time period between the vehicle's engine turning on and the vehicle beginning to travel to a destination;a during travel segment representing a time period during which the vehicle is traveling to said destination and the vehicle's engine remains on; andan end of trip segment representing a time period between the vehicle stopping at said destination and the vehicle's engine turning off.
※ AI-Helper는 부적절한 답변을 할 수 있습니다.