Vehicle Data Context Switching for Fleet Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems and methods for managing vehicle fleets cannot switch contexts to view data interchangeably by drivers or vehicles, limiting their ability to correlate and organize multi-context data in real-time, which is necessary for effective fleet management.

Innovation Solution

Implementing a system and method that processes vehicle operation data to generate and switch contexts between operator- and vehicle-related data, allowing for the correlation of metrics and events to provide a correlated set of data that can be viewed and manipulated interchangeably, enabling real-time association and reporting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If current systems report observations and data in the context of a single entity (operator or vehicle), then data organization is simple, but the system cannot switch contexts to view data interchangeably by drivers or vehicles

Engineering Contradiction:
Improvecontext switching capabilityVSAvoiddata processing complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system dynamically switches between operator context and vehicle context based on user selection. The data processing adapts its organization structure in real-time, transforming static single-entity reporting into dynamic multi-context reporting without requiring separate processing systems for each context.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The same data processing system handles both operator-centric and vehicle-centric views interchangeably. A single processing module serves multiple functions by reorganizing the same underlying data according to different contextual requirements, eliminating the need for separate processing paths.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Speed

If current systems collect operator- and vehicle-related data separately, then data collection is straightforward, but the system cannot organize multi-context data on a real-time basis

Engineering Contradiction:
Improvedata organization speedVSAvoiddata correlation complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system pre-establishes the relational framework between operators and vehicles before data correlation is needed. By having the event associating module pre-identify which operator is operating which vehicle, the system prepares the contextual mapping in advance, enabling real-time data organization without complex runtime calculations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The event associating module acts as an intermediary that links operator data and vehicle data through detected operational events. This mediator component correlates the separately collected data streams by identifying when specific operators are operating specific vehicles, enabling real-time multi-context organization without direct complex processing between all data elements.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If more complex data processing is used to correlate data interchangeably by drivers or vehicles, then context switching is enabled, but real-time data organization becomes difficult

Engineering Contradiction:
Improveinterchangeable data reportingVSAvoiddata processing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system extracts the contextual association information (which operator is operating which vehicle) as a separate identifiable element through the event associating module. By pulling out this contextual metadata from the complex data correlation task, the system can apply simpler, faster processing rules to organize data according to the extracted contextual framework, rather than performing complex queries on the entire dataset.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS9262873B2Systems and methods for processing vehicle data to report performance data interchangeably
Publication Date: 2016.02.16 OMNITRACS LLC
  • US9262873B2 patent drawing
  • US9262873B2 patent drawing
  • US9262873B2 patent drawing

AI summary

Systems and methods to process vehicle operation data are described. A data module associated with a vehicle can collect a set of metrics relating to the operation of the vehicle, as well as events related to an operator's interaction with the vehicle. The data module can correlate the set of metrics with the events to generate a correlated set of data. A user can request various contexts in which to view the data, such as via a vehicle context or an operator context. The data module can generate, using the correlated set of data, a data view according to the request. Further, the correlated set of data and the various contexts can be updated on a real-time basis.