Determining street segment headings
US-2016334221-A1 · Nov 17, 2016 · US
US9865098B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9865098-B2 |
| Application number | US-201213436083-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 30, 2012 |
| Priority date | Mar 31, 2011 |
| Publication date | Jan 9, 2018 |
| Grant date | Jan 9, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
That which is claimed: 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 geographic 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 at least one geographic area during said one or more time periods; identify, based on said operational data, one or more travel delay segments occurring within said at least one geographic area during said one or more time periods, wherein identifying said one or more travel delay segments comprises: 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; 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 at least one geographic area. 2. 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. 3. 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 at least one geographic area comprises a travel delay seconds per mile traveled value. 4. 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 at least one geographic area comprises a miles traveled per travel delay minute value. 5. The fleet management computer system of claim 1 , 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. 6. The fleet management computer system of claim 5 , 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 at least one geographic area. 7. 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 at least one geographic area. 8. The fleet management computer system of claim 7 , 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 at least one geographic area from one or more data storage areas; and loading said certain operational data to said one or more memory storage areas. 9. The fleet management computer system of claim 8 , 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. 10. A non-transitory computer readable storage medium comprising computer executable instructions for: receiving user input data indicating at least one geographic 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 at least one geographic area during said one or more time periods; identifying, based on said operational data, one or more travel delay segments occurring within said at least one geographic area during said one or more time periods, wherein identifying said one or more travel delay segments comprises: 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; 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 at least one geographic area.
Performance of employee with respect to a job function · CPC title
Dispatching vehicles on the basis of a location, e.g. taxi dispatching · CPC title
communicating information to a remotely located station (transmission systems for measured values G08C) · CPC title
Registering or indicating driving, working, idle, or waiting time only (apparatus forming part of taximeters G07B13/00) · CPC title
in graphical form · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.