Asset-Agnostic Framework with Vehicle-Specific Script for Bus Parameter Calculation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing remote asset monitoring systems face limitations in consistently monitoring vehicles of different models and makes due to proprietary standards and varying internal calculations, which affect the usefulness of vehicle bus parameters.

Innovation Solution

A device and method featuring a processor connected to a vehicle bus with asset-agnostic main code and asset-specific script, allowing for vehicle-specific calculations to be performed locally and algorithms to be updated over the air, enabling consistent parameter value calculation across different vehicles.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If proprietary standards and manufacturer-specific parameter calculations are used, then each vehicle can be optimized for its specific make and model, but consistency in monitoring vehicles of different models and makes is compromised

Engineering Contradiction:
Improvevehicle-specific parameter optimizationVSAvoidmonitoring consistency across fleet
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system divides the monitoring solution into two segments: a standardized core framework that ensures consistency across all vehicles, and vehicle-specific script modules that handle make and model variations. This segmentation allows each vehicle type to be optimized independently while maintaining overall fleet consistency through the unified framework.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (the standardized framework with script interfaces) that mediates between proprietary vehicle standards and the central monitoring system. This intermediary translates various manufacturer-specific parameters into a common format, enabling consistent monitoring without sacrificing vehicle-specific optimization.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If vehicle-specific calculation algorithms are hard-coded into the main system, then calculation accuracy can be optimized for each vehicle type, but system updates and maintenance become complex and difficult

Engineering Contradiction:
Improveparameter calculation accuracyVSAvoidsystem update and maintenance complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system separates calculation algorithms into independent, vehicle-specific script segments that can be developed, tested, and updated separately from the main system. Each script handles specific vehicle types, allowing precision optimization without increasing overall system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements dynamic configurability where calculation algorithms can be updated and modified without requiring system reconfiguration or complex maintenance procedures. The modular script architecture allows algorithms to be dynamically adjusted for different vehicle types while maintaining a simple update process.

Inventive Principle:
Principle #15Dynamics

3Ease of manufacture

If a unified main code is used across all vehicles, then system simplicity and ease of deployment are improved, but the ability to handle vehicle-specific variations is limited

Engineering Contradiction:
Improvesystem deployment simplicityVSAvoidvehicle-specific parameter handling
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The main code is designed as a universal platform that can handle multiple vehicle types and standards through a common interface. This universal framework provides ease of deployment while accommodating vehicle-specific variations through configurable script modules that extend the base functionality.

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

Solution Approach 2:

The system segments functionality into a universal main code component and vehicle-specific script components. This segmentation allows the main code to remain simple and easy to deploy, while vehicle-specific requirements are handled by separate, easily configurable script modules.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9916700B2Asset-agnostic framework with asset-specific module for alternate bus parameter calculation
Publication Date: 2018.03.13 GEOTAB INC
  • US9916700B2 patent drawing
  • US9916700B2 patent drawing
  • US9916700B2 patent drawing

AI summary

Network buses in vehicles and other assets are monitored in order to obtain information and calculate alternate values of parameters relating to components connected to the bus and to send them to a management server. The device includes main code, which is common to the different vehicles or assets in a group, and a script, which is specific to each type of vehicle or asset. The script, which may be customizable, is responsible for defining the parameters to obtain and for defining how the values of the parameters are to be calculated. The script compensates for differences in the way different buses and components operate in different assets, which means that the values of like parameters obtained from different sources are all in conformance with each other. The script can be updated without interrupting the operation of the main code and the monitoring of the bus.