Segmenting operational data

• US 9,881,429 B2
• Filed: 05/19/2015
• Issued: 01/30/2018
• Est. Priority Date: 03/31/2011
• Status: Active Grant

• Current Assignee: United Parcel Service Of America Incorporated (United Parcel Service Incorporated)
• Original Assignee: United Parcel Service Of America Incorporated (United Parcel Service Incorporated)
• Inventors: Davidson, Mark J.
• Primary Examiner(s): Black, Thomas G
• Assistant Examiner(s): HUYNH, LUAT T
• Application Number:
  US14/716,160
• Publication Number:
  US 20150262433A1
• Time in Patent Office: 987 Days
• Field of Search: 701 1, 701527, 340438, 340439, 340907, 340990, 340993
• CPC Class Codes: G01C 21/34 Route searching; Route guidance
• CPC Class Codes: G06Q 10/06395 Quality analysis or management
• CPC Class Codes: G06Q 10/08 Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
• CPC Class Codes: G06Q 10/083 Shipping
• CPC Class Codes: G07C 5/008 communicating information to a remotely located station transmission systems for measured values G08C
• CPC Class Codes: G08G 1/0112 from the vehicle, e.g. floating car data [FCD]
• CPC Class Codes: G08G 1/0129 for creating historical data or processing based on historical data
• CPC Class Codes: G08G 1/052 with provision for determining speed or overspeed speed measuring in general G01P
• CPC Class Codes: G08G 1/202 Dispatching vehicles on the basis of a location, e.g. taxi dispatching

Abstract

Computer program products, methods, systems, apparatus, and computing entities are provided for segmenting operational data and identifying events of interest in the segmented operational data. With the events of interest identified, a total time between the events of interest can be determined.

Claims

1. A method for segmenting operational data to determine total elapsed times for events of interest, the method comprising

receiving, by one or more processors, operational data comprising vehicle telematics data and service data, (a) the vehicle telematics data (i) collected by a telematics device affixed to a vehicle and (ii) indicative of one or more vehicle dynamics associated with the vehicle during one or more time periods, and (b) the service data (i) collected by a mobile device operated by a driver of the vehicle and (ii) indicative of one or more service dynamics associated with the driver during the one or more time periods;

segmenting, by the one or more processors, the operational data to identify the occurrence of a plurality of stops during the one or more time periods based at least in part on the operational data, wherein each of the plurality of stops (a) is identified by linking a stop beginning event from the operational data with a stop ending event from the operational data and (b) comprises a stop start time, a stop end time, and a stop type;

identifying, by the one or more processors and based at least in part on the service data, a time of a first event of interest for at least one of the plurality of stops, wherein the service data comprises a timestamp of when the first event of interest occurred;

identifying, by the one or more processors and based at least in part on the vehicle telematics data, a time of a second event of interest for the at least one of the plurality of stops, wherein the vehicle telematics data comprises a timestamp of when the second event of interest occurred;

determining, by the one or more processors, a total time between the first event of interest in the second event of interest; and

indicating, by the one more processors, the total time as the time elapsed for a particular event of interest for the at least one of the plurality of stops.

2. The method of claim 1 further comprising causing display of (a) an indication of each of the plurality of stops and (b) one or more stop attributes for each of the plurality of stops.

3. The method of claim 2, wherein the one or more stop attributes comprise a stop time value indicating the duration of an identified stop.

4. The method of claim 1 further comprising causing display of at least a portion of the plurality of stops in chronological order.

5. The method of claim 1, wherein (a) the first event of interest is an indication that a stop is complete and (b) the second event of interest is an indication of an engine turning on.

6. An apparatus for segmenting operational data to determine total elapsed times for events of interest, the apparatus comprising at least one processor and at least one memory including program code, the at least one memory and the program code configured to, with the processor, cause the apparatus to at least:

receive operational data comprising vehicle telematics data and service data, (a) the vehicle telematics data (i) collected by a telematics device affixed to a vehicle and (ii) indicative of one or more vehicle dynamics associated with the vehicle during one or more time periods, and (b) the service data (i) collected by a mobile device operated by a driver of the vehicle and (ii) indicative of one or more service dynamics associated with the driver during the one or more time periods;

segment the operational data to identify the occurrence of a plurality of stops during the one or more time periods based at least in part on the operational data, wherein each of the plurality of stops (a) is identified by linking a stop beginning event from the operational data with a stop ending event from the operational data and (b) comprises a stop start time, a stop end time, and a stop type;

identify, based at least in part on the service data, a time of a first event of interest for at least one of the plurality of stops, wherein the service data comprises a timestamp of when the first event of interest occurred;

identify, based at least in part on the vehicle telematics data, a time of a second event of interest for the at least one of the plurality of stops, wherein the vehicle telematics data comprises a timestamp of when the second event of interest occurred;

determine a total time between the first event of interest in the second event of interest; and

indicate the total time as the time elapsed for a particular event of interest for the at least one of the plurality of stops.

7. The apparatus of claim 6, wherein the memory and program code are further configured to, with the processor, cause the apparatus to cause display of (a) an indication of each of the plurality of stops and (b) one or more stop attributes for each of the plurality of stops.

8. The apparatus of claim 7, wherein the one or more stop attributes comprise a stop time value indicating the duration of an identified stop.

9. The apparatus of claim 6, wherein the memory and program code are further configured to, with the processor, cause the apparatus to cause display of at least a portion of the plurality of stops in chronological order.

10. The apparatus of claim 6, wherein (a) the first event of interest is an indication that a stop is complete and (b) the second event of interest is an indication of an engine turning on.

11. A computer program product for segmenting operational data to determine total elapsed times for events of interest, the computer program product comprising at least one non-transitory computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising:

an executable portion configured to receive operational data comprising vehicle telematics data and service data, (a) the vehicle telematics data (i) collected by a telematics device affixed to a vehicle and (ii) indicative of one or more vehicle dynamics associated with the vehicle during one or more time periods, and (b) the service data (i) collected by a mobile device operated by a driver of the vehicle and (ii) indicative of one or more service dynamics associated with the driver during the one or more time periods;

an executable portion configured to segment the operational data to identify the occurrence of a plurality of stops during the one or more time periods based at least in part on the operational data, wherein each of the plurality of stops (a) is identified by linking a stop beginning event from the operational data with a stop ending event from the operational data and (b) comprises a stop start time, a stop end time, and a stop type;

an executable portion configured to identify, based at least in part on the service data, a time of a first event of interest for at least one of the plurality of stops, wherein the service data comprises a timestamp of when the first event of interest occurred;

an executable portion configured to identify, based at least in part on the vehicle telematics data, a time of a second event of interest for the at least one of the plurality of stops, wherein the vehicle telematics data comprises a timestamp of when the second event of interest occurred;

an executable portion configured to determine a total time between the first event of interest in the second event of interest; and

an executable portion configured to indicate the total time as the time elapsed for a particular event of interest for the at least one of the plurality of stops.

12. The computer program product of claim 11 further comprising an executable portion configured to cause display of (a) an indication of each of the plurality of stops and (b) one or more stop attributes for each of the plurality of stops.

13. The computer program product of claim 12, wherein the one or more stop attributes comprise a stop time value indicating the duration of an identified stop.

14. The computer program product of claim 11 further comprising an executable portion configured to cause display of at least a portion of the plurality of stops in chronological order.

15. The computer program product of claim 11, wherein (a) the first event of interest is an indication that a stop is complete and (b) the second event of interest is an indication of an engine turning on.