# US 2012/0253632 A1 · Systems and methods for forecasting travel delays

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

- Number: US 2012/0253632 A1
- Document ID: US20120253632A1
- Status: Published application
- Kind: A1
- Application number: 13/436,083
- Filed: 2012-03-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/US20120253632A1

## 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 a fleet management computer system configured for forecasting travel delays within a geographic area. According to various embodiments, the fleet management computer system is configured to assess operational data, including vehicle telematics data. In various embodiments, the fleet management computer system is further configured to determine, based on the operational data, a value indicative of the average amount of travel delay time per unit of distance within the geographic area, such as the average amount of idle time second per mile of travel with the geographic area.

## Claims

### Claim 1

A fleet management computer system for forecasting travel delays within a geographic area, the 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 user input data indicating at least one geographical area;
receive operational data comprising vehicle telematics data, said vehicle telematics data being indicative of one or more vehicle dynamics for at least one vehicle during one or more time periods;
determine, based on said operational data, the distance traveled by said vehicle within said geographical area during said one or more time periods;
identify, based on said operational data, one or more travel delay segments occurring within said geographical area during said one or more time periods;
determine, based on said operational data, the duration of said identified travel delay segments; and
determine, based on said distance traveled and said duration of said travel delay segments, a value indicative of the average amount of travel delay time per unit of distance within said geographic area.

### Claim 2 (depends on 1)

The fleet management computer system of claim 1, wherein said travel delay segments each represent a period of engine idle time occurring while said vehicle was traveling.

### Claim 3 (depends on 1)

The fleet management computer system of claim 1, wherein said value indicative of the average amount of travel delay time per unit of distance within said geographic area comprises a travel delay seconds per mile traveled value.

### Claim 4 (depends on 1)

The fleet management computer system of claim 1, wherein said value indicative of the average amount of travel delay time per unit of distance within said geographic area comprises a miles traveled per travel delay minute value.

### Claim 5 (depends on 1)

The fleet management computer system of claim 1, wherein said processors are configured to identify said travel delay segments by:
segmenting said operational data into a plurality of activity segments representing periods of time classified according to vehicle activity or service activity, said activity segments comprising start of trip segments, travel segments, and end of trip segments; and
identifying, based on said operational data, segments of engine idle time occurring during one of said travel segments and designating said identified engine idle segments as travel delay segments.

### Claim 6 (depends on 5)

The fleet management computer system of claim 5, wherein said processors are further configured to determine, based on said operational data, the average duration of said start of trip segments and the average duration of said end of trip segments.

### Claim 7 (depends on 6)

The fleet management computer system of claim 6, wherein said processors are further configured to:
receive user input data indicating a number of vehicle start and stop events and a distance traveled value; and
determine a total planned idle time value based on said number of vehicle start events, said average duration of said start of trip segments, said number of vehicle stop events, said average duration of end of trip segments, said distance traveled value, and said average amount of travel delay time per unit of distance within said geographic area.

### Claim 8 (depends on 1)

The fleet management computer system of claim 1, wherein said processors are configured to receive said operational data by retrieving certain operational data relating to said user-input geographical area.

### Claim 9 (depends on 8)

The fleet management computer system of claim 8, wherein said processors are configured to receive said operational data by:
receiving user input requesting retrieval of operational data relating to one or more user parameters;
retrieving certain operational data relating to said parameters and said user-selected geographical area from one or more data storage areas; and
loading said certain operational data to said one or more memory storage areas.

### Claim 10 (depends on 9)

The fleet management computer system of claim 9, wherein said one or more user parameters comprise one or more parameters selected from the group consisting of:
one or more time periods;
one or more specific vehicle operators;
one or more specific vehicles; and
one or more locations.

### Claim 11

A computer readable storage medium comprising computer executable instructions for:
receiving user input data indicating at least one geographical area;
receiving operational data comprising vehicle telematics data, said vehicle telematics data being indicative of one or more vehicle dynamics for at least one vehicle during one or more time periods;
determining, based on said operational data, the distance traveled by said vehicle within said geographical area during said one or more time periods;
identifying, based on said operational data, one or more travel delay segments occurring within said geographical area during said one or more time periods;
determining, based on said operational data, the duration of said identified travel delay segments; and
determining, based on said distance traveled and said duration of said travel delay segments, a value indicative of the average amount of travel delay time per unit of distance within said geographic area.
