Vehicle Maintenance System Using Dynamic Wear Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle maintenance systems fail to adapt maintenance intervals to the actual wear status of parts and do not effectively address the needs of drivers and owners regarding cost optimization, trip partitioning, and real-time information provision, particularly in second-hand vehicles.
Innovation Solution
A system comprising a diagnosis plug-in device, host server, and third-party servers, which collects vehicle and route data to enrich user profiles, enabling personalized vehicle maintenance messages and advertisements based on user behavior and vehicle history, ensuring efficient maintenance and cost management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If regular maintenance schedules are followed, then vehicle reliability is maintained, but maintenance costs increase due to unnecessary replacements
Solution Approach 1:
The maintenance system transitions from static scheduled maintenance to dynamic condition-based maintenance. The system continuously monitors actual wear status of parts through collected vehicle data and adapts maintenance intervals dynamically, replacing parts only when actual wear thresholds are reached rather than following fixed schedules.
Solution Approach 2:
The system implements feedback loops where maintenance decisions are continuously refined based on actual vehicle performance data and wear measurements. The host server analyzes collected data, compares actual wear against thresholds, and adjusts future maintenance predictions, creating a closed-loop system that learns from actual vehicle conditions.
2Loss of information
If telematics solutions are implemented, then vehicle data collection is improved, but the system fails to address multiple user needs simultaneously
Solution Approach 1:
The telematics system is designed to serve multiple functions and user groups simultaneously. It collects vehicle data for maintenance prediction, provides trip partitioning for insurance purposes, delivers targeted advertisements to drivers and owners, and supports both first-hand and second-hand vehicle scenarios through a single unified platform.
Solution Approach 2:
The system segments users into different profiles (drivers, owners, insurance companies, advertisers) and segments data processing into specialized modules. Each user group receives customized information and services based on their specific needs, while the underlying data collection infrastructure remains unified.
3Ease of operation
If comprehensive vehicle data is collected and shared with third parties, then personalized services are improved, but system complexity increases
Solution Approach 1:
The host server acts as an intermediary between the diagnosis plug-in device and multiple third-party servers. It centralizes data collection, processing, and distribution, managing communications with insurance companies, advertisers, and maintenance services through a single interface rather than requiring direct connections between all components.
Solution Approach 2:
The system uses data copying and sharing mechanisms where the host server creates and distributes relevant data subsets to different third parties based on their specific needs. Each third party receives customized data copies rather than accessing the complete raw dataset, reducing complexity while maintaining personalization capability.
Data Source
Figure 1~2
Figure 3~5
Figure 6~8
AI summary
Method carried out in a system, the system comprising a diagnosis plug-in device (1), a host server (2), a plurality of third party servers (3) and a user display device (4), the method comprising the following steps: /a/ couple the diagnosis plug-in device (1) to the diagnosis port (8) of the vehicle of interest, /b/ collect, at the diagnosis plug-in device, a basic data set (7) comprising vehicle parameters and route data, including at least vehicle speed, itinerary and geolocations, /c/ transfer the basic data set to the host server (2), /d1/ at the host server, enrich a driver profile relating to the driver of interest and update the vehicle data history of the vehicle of interest, /e1/ forward the basic data set from the host server to the third party servers, /e2/ at the third party servers (31,32,33), enrich a third party driver profile and/or update a third party vehicle data history of the vehicle of interest, /f/ at each third party server, make a decision, based on a set of message issuance criteria, including a user profile authorization profile to receive messages for said particular third party, to build a message for the user and conditions of delivery of this message, said message comprising a vehicle maintenance message and/or advertisement message.