Telematics Data Logger With Access Level Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems for logging telematics data in vehicles and equipment lack efficiency, as they often collect unnecessary data and fail to provide relevant information for timely troubleshooting, due to inadequate access control and data filtering, leading to increased processing power and storage requirements.
Innovation Solution
Implementing a telematics device with access level determination and data filtering capabilities, which logs only relevant data based on predefined access levels and transmits data to a remote computing system only when a specific issue is detected, reducing unnecessary data transmission and storage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If telematics data is continuously logged without filtering, then data availability for troubleshooting is improved, but processing power and storage requirements increase
Solution Approach 1:
The system performs preliminary filtering of telematics data based on access levels before logging, so that only relevant data is stored. This preliminary action reduces the total data volume that requires processing and storage, thereby reducing processing power requirements while maintaining data availability for troubleshooting.
Solution Approach 2:
The system applies different access levels to different data parameters, allowing only relevant data to be logged based on the specific troubleshooting context. This selective logging based on local quality requirements reduces overall data volume and processing demands while ensuring necessary information is preserved.
2Loss of information
If all telematics data is logged regardless of relevance, then diagnostic information completeness is improved, but storage requirements increase
Solution Approach 1:
The system determines the appropriate access level and filters data before logging, performing the selection action in advance. This ensures that only diagnostically relevant data is stored, maintaining information completeness for troubleshooting while minimizing storage requirements by excluding irrelevant data from the beginning.
Solution Approach 2:
The system extracts and logs only the specific subset of telematics data that is relevant to the diagnostic context, separating relevant information from unnecessary data. This extraction approach maintains diagnostic completeness while reducing storage requirements by storing only the essential data subset.
3Loss of information
If data logging starts after fault code is received, then data relevance to the fault is improved, but time delay in capturing fault conditions occurs
Solution Approach 1:
The system determines the access level and prepares filtering criteria in advance based on the fault code context, before the actual data logging begins. This preliminary preparation reduces the setup time and allows data logging to start more quickly, capturing fault conditions with minimal delay while ensuring data relevance through pre-determined filtering criteria.
4Productivity
If access control levels are implemented for data logging, then data filtering efficiency is improved, but system complexity increases
Solution Approach 1:
The system divides data parameters into different access levels (e.g., level 1, level 2, level 3) based on their relevance to troubleshooting. This segmentation allows efficient filtering by simply selecting which level to log, improving data filtering efficiency while keeping the system relatively simple through structured categorization rather than complex algorithms.
Data Source
AI summary
Systems, methods, and apparatuses for automatically logging telematics data are provided herein. An apparatus includes one or more processors, and one or more memory devices storing instructions that, when executed by the one or more processors, cause the one or more processors to: receive access information from a remote computing system, the access information comprising information indicative of a data type and a logging duration; and, log telematics data that corresponds to the data type. Logging the telematics data includes: storing the telematics data that corresponds to the data type in a buffer for the logging duration; monitoring for a fault code; responsive to not detecting the fault code, causing the buffer to delete a portion of the telematics data; and responsive to detecting the fault code, providing the telematics data to the remote computing system.