# US 2012/0253548 A1 · Systems and methods for segmenting operational data

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0253548 A1
- Document ID: US20120253548A1
- Status: Published application
- Kind: A1
- Application number: 13/307,997
- Filed: 2011-11-30
- Published: 2012-10-04
- Earliest claimed: 2011-03-31
- Assignees: United Parcel Service of America, Inc.
- Inventors: Mark J. Davidson
- Web page: https://patentgrep.com/patent/US20120253548A1

## CPC

- G06Q 10/06398: {Performance of employee with respect to a job function}
- G06Q 10/0631: Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G01C 21/3469: {Fuel consumption; Energy use; Emission aspects}
- G01C 21/3617: {using user history, behaviour, conditions or preferences, e.g. predicted or inferred from previous use or current movement}
- G06F 16/29: Geographical information databases
- G06Q 10/08: Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G07C 5/00: Registering or indicating the working of vehicles
- G07C 5/008: {communicating information to a remotely located station (transmission systems for measured values G08C)}
- G07C 5/02: Registering or indicating driving, working, idle, or waiting time only (apparatus forming part of taximeters G07B13/00)
- G07C 5/06: in graphical form
- G08G 1/123: indicating the position of vehicles, e.g. scheduled vehicles; {Managing passenger vehicles circulating according to a fixed timetable, e.g. buses, trains, trams}(transmission of navigation instructions to vehicles G08G1/0968)
- G08G 1/20: {Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles}
- G08G 1/202: {Dispatching vehicles on the basis of a location, e.g. taxi dispatching}
- G08G 1/205: {Indicating the location of the monitored vehicles as destination, e.g. accidents, stolen, rental}
- G08G 1/207: {with respect to certain areas, e.g. forbidden or allowed areas with possible alerting when inside or outside boundaries}
- H04W 4/021: Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G01C: MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY (measuring liquid level G01F; radio navigation, determining distance or velocity by use of propagation effects, e.g. Doppler effects, propagation time, of radio waves, analogous arrangements using other waves G01S)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G07C: TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G08G: TRAFFIC CONTROL SYSTEMS (guiding railway traffic, ensuring the safety of railway traffic B61L; arrangement of road signs or traffic signals E01F9/00; radar or analogous systems, sonar systems, lidar systems specially adapted for traffic control G01S13/91, G01S15/88, G01S17/88; {radar or analogous systems, sonar systems, lidar systems specially adapted for anti-collision purposes G01S13/93, G01S15/93, G01S17/93})
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Various embodiments of the present invention are directed to an efficiency management system configured for evaluating various operational efficiencies based on operational data. In certain embodiments, the efficiency management system is adapted for use as a vehicle fleet management system and configured for receiving operational data from a fleet of vehicles and vehicle operators, and for segmenting the received operational data into a plurality of activity segments. Various embodiments of the vehicle fleet management system may also be further configured for generating a graphical representation of the identified activity segments.

## Claims

### Claim 1

A fleet management computer system comprising:
one or more memory storage areas; and
one or more processors in communication with said one or more memory storage areas;
wherein said one or more processors are, collectively, configured to:
receive operational data comprising vehicle telematics data and service data, said vehicle telematics data being indicative of one or more vehicle dynamics and said service data being indicative of one or more service dynamics; and
segment said operational data into a plurality of activity segments, said activity segments representing periods of time classified according to vehicle activity or service activity.

### Claim 2 (depends on 1)

The fleet management computer system of claim 1, wherein said processors are configured to identify certain of said activity segments based on said vehicle telematics data.

### Claim 3 (depends on 2)

The fleet management computer system of claim 2, wherein said activity segments identified based on said vehicle telematics data comprise start of trip segments, travel segments, travel delay segments, and end of trip segments.

### Claim 4 (depends on 2)

The fleet management computer system of claim 2, wherein said activity segments identified based on said vehicle telematics data comprise on property segments and on area segments.

### Claim 5 (depends on 2)

The fleet management computer system of claim 2, wherein said activity segments identified based on said vehicle telematics data comprise backing segments.

### Claim 6 (depends on 1)

The fleet management computer system of claim 1, wherein said processors are configured to identify certain of said activity segments based on said service data.

### Claim 7 (depends on 6)

The fleet management computer system of claim 6, wherein said activity segments identified based on said service data comprise stop segments.

### Claim 8 (depends on 6)

The fleet management computer system of claim 6, wherein said activity segments identified based on said service data comprise lunch segments, break segments, and coded delay segments.

### Claim 9 (depends on 1)

The fleet management computer system of claim 1, wherein said processors are configured to identify certain of said activity segments based on vehicle telematics data and service data, said activity segments identified based on vehicle telematics data and service data comprising non-travel time to stop segments.

### Claim 10 (depends on 1)

The fleet management computer system of claim 1, wherein said processors are configured to segment said operational data such that every instance of time during one or more operating hours associated with said operational data is classified into one or more of said activity segments.

### Claim 11 (depends on 1)

The fleet management computer system of claim 1, wherein said one or more vehicle dynamics comprise vehicle speed, engine ignition status, and vehicle location.

### Claim 12 (depends on 1)

The fleet management computer system of claim 1, wherein said one or more service dynamics comprise delivery stop commencement, delivery stop completion, package delivery, lunch commencement, lunch completion, break commencement, break completion, coded delay commencement, and coded delay completion.

### Claim 13 (depends on 1)

The fleet management computer system of claim 1, wherein said one or more processors are further configured for generating a graphical representation of one or more of said activity segments.

### Claim 14 (depends on 13)

The fleet management computer system of claim 13, wherein said graphical representation comprises a Gantt chart depicting said activity segments.

### Claim 15 (depends on 1)

The fleet management computer system of claim 1, wherein two or more of the periods of time represented by said activity segments overlap.

### Claim 16 (depends on 1)

The fleet management computer system of claim 1, wherein said processors are further configured for storing said activity segments in one or more memory storage areas, wherein each stored activity segment comprises data indicating a start time, an end time, and a segment name, said segment name being indicative of the activity represented by a respective stored activity segment.

### Claim 17 (depends on 16)

The fleet management computer system of claim 16, wherein each stored activity segment further comprises data indicating a date and at least one of a driver name, driver identification code, vehicle name, and vehicle identification code.

### Claim 18 (depends on 1)

The fleet management computer system of claim 1, wherein said processors are further configured for receiving said vehicle telematics data from one or more vehicle telematics devices, and wherein said processors are further configured for receiving said service data from one or more portable data acquisition devices.

### Claim 19

A computer program product comprising at least one 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, said vehicle telematics data being indicative of one or more vehicle dynamics and said service data being indicative of one or more service dynamics; and
an executable portion configured to segment said operational data into a plurality of activity segments, said activity segments representing periods of time classified according to vehicle activity or service activity.

### Claim 20 (depends on 19)

The computer program product of claim 19, wherein said executable portion configured to segment said operational data into a plurality of activity segments is configured to identify certain of said activity segments based on said vehicle telematics data, wherein said activity segments identified based on said vehicle telematics comprise one or more segments selected from the group consisting of: start of trip segments, travel segments, travel delay segments, end of trip segments, on property segments, on area segments, and backing segments.

### Claim 21 (depends on 19)

The computer program product of claim 19, wherein said executable portion configured to segment said operational data into a plurality of activity segments is configured to identify certain of said activity segments based on said service data, wherein said activity segments identified based on said service data comprise one or more segments selected from the group consisting of: lunch segments, break segments, and coded delay segments.

### Claim 22 (depends on 19)

The computer program product of claim 19, wherein said executable portion configured to segment said operational data into a plurality of activity segments is configured to identify certain of said activity segments based on vehicle telematics data and service data, said activity segments identified based on vehicle telematics data and service data comprising non-travel time to stop segments.

### Claim 23 (depends on 19)

The computer program product of claim 19, wherein said executable portion configured to segment said operational data into a plurality of activity segments is configured to segment said operational data such that every instance of time during one or more operating hours associated with said operational data is classified into one or more of said activity segments.

### Claim 24 (depends on 19)

The computer program product of claim 19, wherein said one or more service dynamics comprise delivery stop commencement, delivery stop completion, package delivery, lunch commencement, lunch completion, break commencement, break completion, coded delay commencement, and coded delay completion.

### Claim 25 (depends on 19)

The computer program product of claim 19, wherein the computer-readable program code portions further comprise an executable portion configured for generating a graphical representation of one or more of said activity segments.

### Claim 26 (depends on 19)

The computer program product of claim 19, wherein said executable portion configured to receive operational data is configured for receiving said vehicle telematics data from one or more vehicle telematics devices and receiving said service data from one or more portable data acquisition devices.

### Claim 27

A method for evaluating operational efficiencies of a fleet, said method comprising the steps of:
receiving, via a computer system, operational data comprising vehicle telematics data and service data, said vehicle telematics data being indicative of one or more vehicle dynamics and said service data being indicative of one or more service dynamics; and
segmenting said operational data into a plurality of activity segments, said activity segments representing periods of time classified according to vehicle activity or service activity.

### Claim 28 (depends on 27)

The method of claim 27, wherein said step of segmenting said operational data into a plurality of activity segments includes identifying certain of said activity segments based on said vehicle telematics data, wherein said activity segments identified based on said vehicle telematics comprise one or more segments selected from the group consisting of: start of trip segments, travel segments, travel delay segments, end of trip segments, on property segments, on area segments, and backing segments.

### Claim 29 (depends on 27)

The method of claim 27, wherein said step of segmenting said operational data into a plurality of activity segments includes identifying certain of said activity segments based on said service data, wherein said activity segments identified based on said service data comprise one or more segments selected from the group consisting of: lunch segments, break segments, and coded delay segments.

### Claim 30 (depends on 27)

The method of claim 27, wherein said step of segmenting said operational data into a plurality of activity segments includes identifying certain of said activity segments based on vehicle telematics data and service data, said activity segments identified based on vehicle telematics data and service data comprising non-travel time to stop segments.

### Claim 31 (depends on 27)

The method of claim 27, wherein said step of segmenting said operational data into a plurality of activity segments includes segmenting said operational data such that every instance of time during one or more operating hours associated with said operational data is classified into one or more of said activity segments.

### Claim 32 (depends on 27)

The method of claim 27, wherein said one or more service dynamics comprise delivery stop commencement, delivery stop completion, package delivery, lunch commencement, lunch completion, break commencement, break completion, coded delay commencement, and coded delay completion.

### Claim 33 (depends on 27)

The method of claim 27, further comprising the step of generating a graphical representation of one or more of said activity segments.

### Claim 34 (depends on 27)

The method of claim 27, wherein said step of receiving, via a computer system, operational data comprising vehicle telematics data and service data includes receiving said vehicle telematics data from one or more vehicle telematics devices and receiving said service data from one or more portable data acquisition devices.
