Vehicle Data Acquisition via Dynamic Definition Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data collection and reporting systems for vehicles require manual operations to ensure data reports match software updates, leading to reduced accuracy and usefulness of collected data.
Innovation Solution
A method and system where a data acquisition definition file is defined and communicated via a two-way electronic link between a data collection and reporting hub and a data acquisition system, allowing automatic detection and updating of vehicle build configurations and corresponding data acquisition definition files, eliminating the need for manual updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If manual operations are performed to update data reports after software updates, then data report accuracy can be maintained, but time consumption and operational complexity increase
Solution Approach 1:
The system performs preliminary actions by pre-defining data report templates and configurations at the hub before software updates occur. When software updates are deployed to vehicles, the hub proactively pushes updated data acquisition definition files to vehicles, eliminating the need for manual post-update operations and reducing time consumption while maintaining accuracy.
Solution Approach 2:
The system establishes a feedback mechanism where vehicles report their software versions and build configurations to the hub. The hub compares this information against its records, automatically detects mismatches between software updates and data report configurations, and triggers automated updates to synchronize data acquisition parameters with the latest software versions.
2Reliability
If manual operations are performed to synchronize data reports with software updates, then data consistency can be maintained, but operational complexity increases
Solution Approach 1:
The system enables self-service by allowing vehicles to automatically report their software versions and build configurations to the hub. The hub autonomously compares this information with its database, identifies mismatches, and automatically pushes updated data acquisition definition files to vehicles, eliminating manual intervention entirely and reducing operational complexity while maintaining data consistency.
Solution Approach 2:
The hub acts as an intermediary between software update management and data acquisition systems. It receives software version information from vehicles, processes this information against its database of build configurations, and automatically generates and pushes the appropriate data acquisition definition files, thereby simplifying the synchronization process and reducing operational complexity.
3Loss of time
If automated data acquisition definition file distribution is implemented, then time consumption and operational complexity are reduced, but system complexity increases
Solution Approach 1:
The hub performs multiple functions within a single system: it stores software version information, maintains build configuration databases, compares vehicle reports against its records, generates updated data acquisition definition files, and distributes them to vehicles. This multi-functionality consolidates what would otherwise require multiple separate systems, reducing overall system complexity while enabling automated operations.
Solution Approach 2:
The system implements a nested structure where the hub contains an embedded database of build configurations and software version information. When vehicles report their status, the hub's comparison module nests within this database structure to automatically identify mismatches and trigger the appropriate update procedures, creating a compact integrated system that reduces complexity.
Data Source
AI summary
A method of data collection for a vehicle includes defining a vehicle build configuration based on individual build configurations of one or more vehicle systems, and defining a data acquisition definition file at a data collection and reporting hub based on the vehicle build configuration. The data acquisition definition file includes parameters and measurements to be performed by a data acquisition system located at the vehicle. The data acquisition definition file is requested by the data acquisition system and the data acquisition definition file is communicated to the data acquisition system via a two way electronic communication link between the data collection and reporting hub following the request from the data acquisition system. Vehicle data is collected at the data acquisition system based on the data acquisition definition file.