JP2017117193A - Vehicle information management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To identify the cause of malfunctions such as a vehicular failure more accurately and quickly on the basis of diagnostic information from a vehicle and feeds back those pieces of information to the development, production, sales, maintenance and the like of the vehicle.SOLUTION: A vehicle information management system includes: event detection means for detecting event information occurring to a vehicle; a data server managed by a data manager of a maker and the like; event information output means for outputting the event information to the data server; analysis information generation means for generating analysis information on the basis of accumulated event information; and terminal means for feeding back the analysis information to a system user. For the event information, event category data, at production data, region data; component data, travel distance data and maintenance data are correlated with each event that has occurred. The analysis information contains, for the same event category, event tendency analysis data that accumulates event information on the basis of an element selected from individual element per piece of: at-production data; region data; component data; travel distance data; and maintenance data.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a vehicle information management system that manages information related to failures, defects, and the like that have occurred in a vehicle, and uses such information for vehicle design, manufacture, maintenance, and the like.

  The electronic control unit provided in the vehicle has a function of self-diagnosis of a prime mover such as an engine or a motor, auxiliary equipment added thereto, sensors for obtaining information from them, a failure or a malfunction of a device for controlling them. It is often provided.

  Information obtained by this self-diagnosis function is also called diagnostic information, and a dealer or the like who performs maintenance can grasp the presence or content of the diagnostic information by connecting a specific device to the connector of the electronic control unit. It is like that.

  In addition, diagnostic information detected by the electronic control unit, for example, “failure code” indicating the type of failure, “sensor value” indicating an abnormal numerical value, and “vehicle information” such as the model of the vehicle associated therewith, etc. Are stored in a server of an information management system managed by a vehicle manufacturer, a sales company, or the like through information communication equipment such as wired communication or a recording medium.

  In this type of information management system, the server administrator analyzes the data of the diagnostic information to enable early detection of defects at vehicle manufacturers and early notification of problems to users, dealers, etc. Various proposals have been made.

  For example, in Patent Document 1, a region of the vehicle is determined from vehicle traveling position information attached to the received diagnosis information, and defect information and repair information are grasped for each region (city area, mountainous area, etc.) and information is accumulated. Based on these, rule information is created for each region. By applying newly received diagnostic information to this rule information and estimating the cause of the failure, the time required to identify the cause of the failure when the vehicle has a failure is reduced. .

JP 2010-14498 A

  However, the technique disclosed in Patent Document 1 has a problem that even if the rule information is in the same region, the way the vehicle is used differs depending on the stored vehicle type, grade, and the like. For example, even if it is the rule information of the same area, the acceleration / deceleration of the vehicle, the use frequency, and other driving conditions differ depending on whether the vehicle is a sporty type or a wagon type.

  If these operating conditions are different, the load on the engine and power transmission path of the vehicle and the members and parts of each part associated therewith also vary. For this reason, it is often difficult to identify the cause of the failure early based only on the rule information for each region.

  Therefore, the problem of the present invention is to identify the cause of the failure or malfunction of the vehicle more accurately and quickly based on the diagnosis information from the vehicle, and use that information for vehicle development, manufacturing, sales, maintenance, etc. It is to give feedback.

  In order to solve the above problems, the present invention is managed by event detection means for detecting event information based on an event such as a malfunction or repair that has occurred in a vehicle, and a data manager such as a vehicle manufacturer or a seller. A data server, event information output means for outputting the event information from a vehicle to the data server, analysis information creation means for creating analysis information based on the event information stored in the data server, Terminal means for feeding back analysis information to the data manager or a system user permitted to connect to the data server, and the event information is the occurrence of the event for each event that has occurred. Event type data indicating contents and parts, manufacturing time data indicating information at the time of manufacturing the vehicle, and component data indicating the type of equipment mounted on the vehicle are associated with each other. It is for the same event type, specific production time of data, including an event trend analysis data for storing the event information based on the component data by the respective elements, employing an information management system for a vehicle.

  At this time, the event information is performed for each event that has occurred, the region data indicating the region in which the vehicle travels, the travel distance data indicating the travel distance from a new registration or a predetermined period, and the vehicle. Maintenance data is associated, and the analysis information is selected from each element for each region data, each mileage data, and each maintenance data in addition to each manufacturing data and component data for the same event type. A configuration including event trend analysis data that accumulates the event information based on a single element or a plurality of elements may be employed.

  Here, when the generated event information matches the event trend analysis data, the terminal means uses the matched event trend analysis data as feedback information for specifying the cause of the event. A configuration obtained from the data server can be adopted.

  In addition, the terminal means feeds back the event trend analysis data in which the accumulated number of event information corresponding to each of the selected elements is equal to or greater than a predetermined accumulated number, to identify the cause of the occurrence of those events A configuration obtained from the data server as information can be employed.

  The event information may employ a configuration including vehicle format data, vehicle manufacturing time data, and vehicle manufacturing line data as the manufacturing time data.

  In each of these configurations, a travel position detecting means for recognizing the area in which the vehicle is traveling is provided, and the regional data is that the vehicle is traveling when the event occurs for each event that has occurred. A configuration can be adopted in which the area is acquired by the travel position detecting means.

  In addition, the component data employs a configuration including original data indicating devices mounted at the time of manufacture of the vehicle and option data indicating an attachment state of an optional attachment that can be selectively attached to the vehicle. be able to.

  The event type data may employ a configuration composed of a combination of content data indicating the content of the event and component data related to the site where the event has occurred.

  The event type data includes an event code determined according to a combination of the content data and the component data, and the event code is stored in an engine or an electronic control unit that controls the engine when the event occurs. The image information output means may employ a configuration in which various sensor values at the time of event occurrence and control data at the time of event occurrence are output from the vehicle to the data server together with the event code.

  The manufacturing time data and the component data are managed by the data manager or a system user permitted to connect to the data server based on the event information output from the vehicle to the data server. The configuration provided by can be adopted.

  The present invention accumulates event information output at the time of occurrence of an event such as a failure or malfunction in a data server, and the accumulated event information is classified by component data at the time of manufacture, by regional data, and further if necessary. Event trend analysis was conducted under conditions such as separate, mileage data, maintenance data, etc., and the information on the event trend analysis should be fed back to developers, manufacturers, maintainers, etc. Can do. This makes it possible to reduce warranty costs by early detection of defects.

It is a schematic diagram which shows the system configuration | structure of this invention. It is a schematic diagram which shows the structure of event information. (A)-(c) is a chart which shows the example of analysis information. It is a flowchart which shows this invention.

  An embodiment of the present invention will be described with reference to the drawings. This embodiment is a vehicle information management system that manages information related to breakdowns, malfunctions, and the like that occur in a vehicle and repairs that have been made to the vehicle, and uses such information for vehicle design, manufacturing, maintenance, and the like. .

  As shown in FIG. 1, the electronic control unit 2 provided in the vehicle 1 includes a prime mover such as an engine and a motor, auxiliary equipment added thereto, sensors for obtaining information from them, a failure of a device for controlling them, It has a function to self-diagnose malfunctions. This self-diagnosis function may be provided by the engine itself or the accessories itself.

  Information obtained by this self-diagnosis function is also called diagnosis information, but this information is hereinafter referred to as “event information”. By connecting a specific device to the connector provided in the electronic control unit 2, vehicle manufacturers, sales companies, and the like can grasp the presence and content of the diagnostic information through information communication devices such as wired communication and recording media. ing.

  In the present invention, the event information is stored in the data server 10 managed by a data manager such as a vehicle manufacturer or a sales company through the information transmission device 3 by wireless communication. Note that event information may be stored in the data server 10 using wired communication, a recording medium, or the like, or may be used in combination with wireless communication.

  The specific configuration of the vehicle information management system consists of event detection means for detecting event information based on events such as malfunctions and repairs occurring in the vehicle, and data managed by a data manager such as a vehicle manufacturer or seller. A server 10 and event information output means for outputting event information from the vehicle to the data server 10 are provided. In this embodiment, the electronic control unit 2 plays the role of event detection means. Further, the role of event information output means is played by a telematics in-vehicle device mounted as the information transmission device 3 by wireless communication.

  Further, the vehicle information management system includes analysis information creation means for creating analysis information based on event information accumulated in the data server 10, and a system in which the analysis information is permitted to be connected to the data manager or the data server. And terminal means 20 for feeding back to the user. In this embodiment, the analysis information creation means is provided in the terminal means 20 of the data manager or system user who can access the data server 10, but the analysis information creation means is provided in the analysis terminal provided in the data server 10. The information may be transmitted from the analysis terminal to the terminal means 20.

  The terminal means 20 of the system user is managed by a person who is permitted to access the data server 10 from the data manager. Within a vehicle manufacturer, for example, a terminal 21 of a quality manager, a terminal 22 of a developer, and a terminal 24 at a vehicle manufacturing plant (manufacturing factory) are exemplified. In the sales company, there is a terminal 23 of a vehicle seller (store). The data manager includes a dedicated terminal 25 as the terminal means 20. The terminal means 20 of the seller or the factory has a local server for storing information.

  The event information 30 output from the vehicle 1 to the data server 10 includes, as shown in FIG. 2, event type data 31 indicating the content and part of the event for each event that has occurred in the vehicle 1, Area data 32 indicating the area in which the vehicle travels, travel distance data 33 indicating the distance traveled for a predetermined period from the time of new registration, manufacturing time data 41 indicating information at the time of manufacture of the vehicle, and the type of equipment mounted on the vehicle Component data 42 and maintenance data 43 performed on the vehicle are associated with each other.

  The event type data 31, the regional data 32, and the travel distance data 33 are information held by the electronic control unit 2 of the vehicle 1. The regional data 32 and the travel distance data 33 are output to the data server 10 as event information 30 together with the event type data 31 of the event.

  The regional data 32 is acquired by the traveling position detection means 4 that recognizes the area where the vehicle is traveling, using a global positioning system (global positioning system) provided in the vehicle 1. That is, in the area data 32, when an event occurs in the vehicle 1, the area in which the vehicle 1 is traveling is acquired by the traveling position detection unit 4, and the position information is associated with the event type data 31. It is also possible to use information on the registered area of the vehicle 1 as the area data 32.

  The travel distance data 33 is acquired by a distance accumulator provided in the vehicle 1. The total travel distance from the time of new registration and the travel distance for a predetermined period, for example, the travel distance for the last one month, half year, year, etc. are acquired, and the travel distance information is associated with the event type data 31. .

  The manufacturing time data 41 is information held by a local server in a vehicle manufacturing plant. The component data 42 is information held by a local server in a vehicle manufacturing plant and a vehicle sales store. The manufacturing time data 41 and component data 42 are provided to the data server 10 from the terminal 24 at the vehicle manufacturing site and the terminal 23 of the vehicle dealer, respectively, based on the event information output from the vehicle 1 to the data server 10. . Since the event information 30 includes a chassis number, a registration number, and the like of the vehicle 1, information can be provided in response to a request from the terminal means 20 through these numbers.

  Further, the production time data 41 includes vehicle 1 format data 41a, vehicle 1 production time data 41b, and vehicle 1 production line data 41c. The format data 41a includes information such as the vehicle type, model number, identification number, and grade of the vehicle 1. The manufacturing time data 41b includes the year and month when the vehicle 1 is manufactured, and the manufacturing line data 41c includes the name of the factory where the vehicle 1 is manufactured and the name of the manufacturing line in the factory.

  The component data 42 includes original data 42 a indicating devices mounted at the time of manufacturing the vehicle 1 and option data 42 b indicating an attachment state of an optional attachment that can be selectively attached to the vehicle 1. As a device (component) whose contents are registered as the original data 42a, a large classification includes, for example, an engine, an air conditioner, a transmission, a power steering, an electric motor, and a battery. More detailed items are registered as the medium category and the small category. Examples of the option-installed product registered as the option data 42b include a car navigation system.

  The maintenance data 43 is information held by a vehicle seller or a maintenance factory. In this embodiment, the seller also serves as a maintenance shop, but there is an example where these are separate. In this case, the maintenance factory has its own terminal means 20 and local server. Maintenance information (information relating to maintenance history) performed on the vehicle 1 is data based on the event information 30 output from the vehicle 1 to the data server 10 through the terminal means 20 in the vehicle seller or manufacturing factory, respectively. Provided to the server 10.

  The event type data 31 includes a combination of content data 31a indicating the content of the event and component data 31b related to the site where the event has occurred.

  Usually, as the event type data 31, an event code 31c determined according to the combination of the content data 31a and the component data 31b is set. Therefore, it is possible to grasp what kind of failure or malfunction has occurred in which part of the vehicle 1 by the event code 31c. The event code 31c is stored in the electronic control unit 2 when an event occurs. However, the event code 31c does not necessarily identify the cause of the event, and even if the content data 31a and the part data 31b are accompanied, what is wrong with the part, the manufacturing reason, In many cases, it is not possible to grasp whether this is due to the use of the user or the reason.

  When the event occurs, the event information output means 3 included in the vehicle 1 outputs various sensor values 31d when the event occurs and control data 31e when the event occurs from the vehicle 1 to the data server 10 along with the event code 31c. . As a result, the event information 30 has a form in which various sensor values 31d and control data 31e at the time of the event accompany the event code 31c.

  Based on the event information 30 stored in the data server 10, the analysis information creation means creates the analysis information 50 as information for specifying the cause of the event. An example of the analysis information 50 is shown in the chart of FIG.

  The analysis information 50 of FIG. 3 is a single item selected from each element of manufacturing data, region data, component data, mileage data, and maintenance data for the same type of event type data 31. Alternatively, event trend analysis data for classifying and accumulating the event information 30 based on a plurality of factors.

  Here, in order to create the analysis information 50, five layers are set as input elements. For example, in FIG. 3 (a), the event code 31c of the event type data 31 which is an essential input item for the tier 1, the regional data 32 as the tier 2, and the format data (vehicle type) from the manufacturing time data 41 as the tier 3. ) 41a is input as production level data 41b as hierarchy 4 and production line data 41c as hierarchy 5.

  Further, for example, in FIG. 3B, the event code 31c of the event type data 31 which is an indispensable input item for the layer 1, the regional data 32 as the layer 2, and the format data from the manufacturing time data 41 as the layer 3 (Vehicle type) 41a is input as travel distance data 33 as level 4 and manufacturing factory data as level 5. Since the manufacturing factory data is included in the manufacturing line data 41c, such input is also possible.

  Further, for example, in FIG. 3C, the event code 31 c of the event type data 31 that is an indispensable input item for the layer 1 is used, the format data (vehicle type) 41 a is selected from the manufacturing time data 41 as the layer 2, and the layer 4 is used. Manufacturing line data 41c and maintenance data 43 as level 5 are input.

  By setting these elements, the accumulated number of event information 30 corresponding to each of the selected elements of the plurality of layers is calculated. That is, the accumulated number of event information 30 that matches the five selected conditions is shown.

  Here, the terminal means 20 uses data (hereinafter referred to as “event trend analysis”) in which the accumulated number of event information 30 corresponding to each of the selected elements of the five hierarchies is equal to or greater than a predetermined accumulated number. Data ”) is acquired from the data server 10 as feedback information for specifying the cause of these events.

  In these event trend analysis data, for example, in FIG. 3 (a), an event occurred in a vehicle manufactured by a specific production line in the vehicle group corresponding to the same event code, region, vehicle type, and production time. It is possible to ascertain cases where the accumulated number of is extremely greater than that of vehicles manufactured by other manufacturing lines. For this reason, it can be presumed that some circumstances related to the malfunction occurred in a specific production line and a specific part of a specific vehicle type at a specific time.

  In addition, for example, in FIG. 3B, the accumulated number of events that have occurred in a vehicle manufactured by a specific manufacturing factory in a group of vehicles corresponding to the same event code, region, vehicle type, and similar travel distance. However, it is possible to grasp cases and the like that are extremely greater than those of vehicles manufactured by other manufacturing factories.

  Furthermore, in FIG. 3 (c), the same event code, region, vehicle type, production line, and the same replacement parts a at the time of maintenance occur in vehicles that exceed the predetermined age. It is possible to grasp the cases where the number of accumulated events is extremely larger than that of vehicles with less than a few years. For this reason, how much trouble is expected to occur when a model manufactured on a specific production line passes a predetermined number of years (for example, 20% if 3 years have passed, 50% if 5 years have passed) It is possible to predict the occurrence of a component failure with probability and specify the cause of the failure.

  Note that the predetermined accumulation number serving as a threshold for determining the quality of the accumulation number may be determined in advance as the number of event occurrences serving as a reference for determining abnormality, or the five selected hierarchies The predetermined accumulation number serving as a threshold value may be determined based on a reference ratio that must not exceed the total number of vehicles corresponding to each of the elements.

  Event trend analysis data when the accumulated number of event information 30 is equal to or greater than the predetermined accumulated number may be acquired by the terminal means 20 in response to a request from the terminal means 20 of the system user. When the accumulated number of 30 is equal to or greater than the predetermined accumulated number, it may be automatically transmitted to the terminal means 20 of the system user.

  In the example of FIG. 3, five layers are set as elements to be set for creating the analysis information 50 and the contents of each element are input to each layer. However, when the analysis information 50 is created, The number of elements to be set is arbitrary. For example, one element may be set for the event type data 31, or two, three, or more elements may be set. . Further, as the event information 30, the sensor value 31d or the control data 31e when the event occurs may be added as input.

  For example, as shown in FIG. 1, for the event type data 31, only the original data 42 a is set from the regional data 32, the format data (vehicle type) 41 a from the manufacturing time data 41, and the component data 42. The analysis information 50 may be created with elements consisting of four layers.

  By utilizing such event trend analysis data, not only the “use region” of the vehicle 1 but also “how the vehicle is used” and “vehicle characteristics” that vary greatly depending on the type of the vehicle 1 are taken into consideration. The event information 30 can be stored for each vehicle type and part. Also, manufacturing data 41 and component data 42 of the vehicle 1 (manufacturing line name, date and time of manufacture, mounted equipment, parts used, mounting options, etc.), maintenance data 43 at the dealer (maintenance history, vehicle inspection results, replacement parts, etc.) ) Can be taken into account.

  Thereby, the tendency of the failure and malfunction which generate | occur | produce in the vehicle 1 can be grasped | ascertained at an early stage. By grasping the tendency of failure or failure, the cause of the failure or failure can be identified earlier. In other words, the accumulated event information 30 can be analyzed based on each element such as regional data, mileage data, manufacturing data, component data, maintenance data, etc. By analyzing the corresponding event trends, it is possible to feed back information to vehicle designers, developers, and maintainers at an early stage, and it is possible to reduce warranty costs by early detection of failures and malfunctions.

  In addition, even if the vehicle 1 travels in the same region, the usage of the vehicle 1 differs depending on the stored vehicle type and grade, and the vehicle is of a sporty type or of a wagon type. Depending on whether or not, the vehicle acceleration / deceleration, frequency of use, and other driving conditions differ.

  Considering the difference in use conditions, by applying the event information 30 from the vehicle 1 to the event trend analysis data, the event information 30 consisting of the same elements as the elements of each layer included in the event information 30 Can be found in. That is, by identifying the past event information 30 that matches the content of the event content 30 of the generated event in the analysis information 50, the cause of the failure or malfunction of the vehicle 1 can be identified more accurately and quickly, Information can be fed back to vehicle development, manufacturing, sales, maintenance, etc.

  Whether or not information that matches the newly output event information 30 is accumulated in the analysis information 50 is determined by setting a threshold as in the above example and extracting only the analysis information 50 that is equal to or higher than the threshold. Alternatively, all matching analysis information 50 may be extracted without providing a threshold value.

  FIG. 4 shows an example of a flowchart relating to the accumulation of event information, creation of analysis information, and feedback of event trend analysis data using this vehicle information management system.

  In step S 1, control is started. In step S 2, when an event occurs in the vehicle 1, the event information 30 is output from the vehicle 1 to the database 10. If no event has occurred, step S2 is repeated.

  When the event occurs, in step S3, the data server 10 of the data manager acquires the manufacturing time data 41 and the component data 42 related to the corresponding vehicle 1 from the database of the local server of the manufacturing facility.

  Subsequently, in step S4, the data server 10 of the data manager acquires the maintenance data 43 related to the corresponding vehicle 1 from the database of the seller's local server.

  In step S <b> 5, event type data 31, production time data 41, component data 42, and maintenance data 43 are associated as event information 30. In step S6, event type data 31, area data 32, travel distance data 33, and other data are associated as event information 30.

  In step S7, the accumulated event information 30 is analyzed, and analysis information 50 is created.

  In step S8, it is determined whether or not the event information 30 output from the vehicle 1 is in the analysis information 50. If past event information 30 that matches the content of the event content 30 of the event that has occurred is found in the analysis information 50, the process proceeds to step S9, and the matched event information 30 and the content information of the analysis information 50 are notified to the developer. To do. By analyzing the elements of the matched analysis information 50, the cause of the failure or malfunction of the vehicle 1 can be identified more accurately and quickly, and such information can be fed back to vehicle development, manufacturing, sales, maintenance, etc. Can do. If there is no matching information in the analysis information 50, the process proceeds to step S13, the information is accumulated, and the system control is terminated.

  Next, in step S10, it is determined whether or not the output event information 30 can determine the cause of the event. If the factor can be determined, the process proceeds to step S11. If the cause cannot be determined, the process proceeds to step S13, information is accumulated, and the control is terminated. Here, the determination of the factor is not a level at which a clear factor is specified, but a level at which an approximate site where the event has occurred and the content can be specified.

  In step S11, regarding the event information 30 output this time, from among a plurality of pieces of information associated with the event information 30, an element of each hierarchy to be input in an arbitrary combination or a preset combination is determined. It is determined whether or not there is an analysis information 50 corresponding to the determined element whose accumulated number is equal to or greater than a predetermined accumulated number. Here, if elements are set in any combination, it can be set to automatically extract the combination from all the associated information, and all possible combinations can be verified. It can also be set.

  If there is an information accumulation number that is greater than or equal to the predetermined accumulation number, it is considered that many events similar to the event that occurred this time have occurred under the conditions of the elements of each determined hierarchy, It can be inferred that there is an event factor in the content of the input element. This event trend analysis data is output to the terminal means 20 of the maintenance person of the vehicle 1 as necessary in addition to notifying the designer, developer, etc. in step S12, and immediately fed back as information. After the information is output, the information is stored in the data server 10 in step S13, and the system control is terminated.

  If the accumulated number of information is less than the predetermined accumulated number, it is considered that an event similar to the event that has occurred this time has not occurred so much, so the terminal server 20 is not notified and output, and in step S13 the data server The information is stored in 10, and the system control is terminated.

DESCRIPTION OF SYMBOLS 1 Vehicle 2 Electronic control unit 3 Event information output means 4 Traveling position detection means 10 Data server 20 Terminal means 30 Event information 31 Event classification data 32 Area data 33 Travel distance data 41 Manufacturing data 42 Component data 43 Maintenance data 50 Analysis information

Claims (10)

An event detection means for detecting event information based on an event such as a malfunction or repair occurring in the vehicle;
A data server managed by a data manager such as a vehicle manufacturer or seller,
Event information output means for outputting the event information from a vehicle to the data server;
Analysis information creating means for creating analysis information based on the event information stored in the data server;
Terminal means for feeding back the analysis information to the data manager or a system user permitted to connect to the data server;
With
The event information includes, for each event that occurs, event type data indicating the content and part of the event, manufacturing time data indicating vehicle manufacturing information, and the type of equipment mounted on the vehicle. The component data shown is associated,
The analysis information includes event trend analysis data for accumulating the event information based on each element of manufacturing data and component data for the same event type,
Vehicle information management system. The event information includes, for each event that has occurred, regional data indicating the region in which the vehicle travels, travel distance data indicating the travel distance for a predetermined period of time since new registration, and maintenance data performed on the vehicle Is associated,
The analysis information is a single element or a plurality of elements selected from each element for each region data, each mileage data, and each maintenance data in addition to each manufacturing data and each component data for the same event type. Including event trend analysis data that accumulates said event information based on:
The vehicle information management system according to claim 1. When the generated event information matches the event trend analysis data, the terminal means uses the matched event trend analysis data as the feedback information for specifying the cause of the event. The vehicle information management system according to claim 1, which is acquired from a server. The terminal means uses the event trend analysis data in which the accumulated number of event information corresponding to each of the selected elements is equal to or greater than a predetermined accumulated number as feedback information for identifying the cause of the occurrence of those events. The information management system for vehicles according to claim 1 or 2 acquired from said data server. 5. The vehicle information management system according to claim 1, wherein the event information includes vehicle format data, vehicle manufacturing time data, and vehicle manufacturing line data as the manufacturing time data. A traveling position detecting means for recognizing an area where the vehicle is traveling;
The area data is acquired by the travel position detecting means for each event that occurs, an area in which the vehicle is traveling when the event occurs. Vehicle information management system. The component data includes original data indicating a device mounted at the time of manufacture of the vehicle and option data indicating an attachment state of an optional attachment that can be selectively attached to the vehicle. The vehicle information management system according to claim 1. The said event classification data are comprised by the combination of the content data which shows the content in which the event happened, and the component data relevant to the site | part in which the event occurred. Vehicle information management system. The event type data includes an event code determined according to a combination of the content data and the component data, and the event code is stored in an engine or an electronic control unit that controls the engine when an event occurs.
9. The vehicle information management system according to claim 8, wherein the event information output means outputs various sensor values when an event occurs and control data when the event occurs together with the event code from the vehicle to the data server. The manufacturing time data and the component data are managed by the data manager or a system user permitted to connect to the data server based on the event information output from the vehicle to the data server. The vehicle information management system according to any one of claims 1 to 9, provided by:

Images