JP7620263B2 - Information processing device - Google Patents

Description

The present invention relates to an information processing device suitable for use in manufacturing vehicles that reflect user needs.

When it comes to selling vehicles such as four-wheeled automobiles, the customer selects and purchases a product whose design and specifications are provided by the manufacturer. This makes it difficult to meet the customer's specific needs, such as minor vehicle options, designs, and functions.

On the other hand, for products other than vehicles, systems are known that process and manage products based on the standards and specifications required by users (see, for example, Patent Document 1). Such systems allow users to obtain products that reflect detailed options, etc.

JP 2002-328972 A

However, if the system disclosed in Patent Document 1 were to try to accommodate all of the detailed options of all users, there would be problems such as a significant increase in manufacturing costs and extremely complicated methods of processing and managing the products.

The present invention was made in consideration of the above-mentioned circumstances, and one of its objectives is to provide vehicles that meet the needs of users at a realistic cost.

The information processing device according to one aspect of the present disclosure includes a collection unit that collects customization information for a vehicle desired by a user, a database that registers vehicle model information for each selectable vehicle, an identification unit that identifies vehicle model information for a vehicle required to realize the user's desire from among multiple vehicle model information registered in the database based on the customization information, a generation unit that generates request information based on the identified vehicle model information and customization information, a transmission unit that transmits the generated request information to a manufacturing candidate, a reception unit that receives proposal information for a customized vehicle that reflects the request information from the manufacturing candidate, and an output unit that outputs the received proposal information.

According to certain aspects of the present invention, it is possible to provide vehicles that meet the needs of users at a realistic cost.

FIG. 1 is an explanatory diagram showing an overview of a system according to an embodiment of the present invention. FIG. 1 illustrates an example of a system configuration. FIG. 2 is a diagram illustrating an example of a hardware configuration of a vehicle proposal server and a terminal. FIG. 2 is a block diagram showing a functional configuration of a vehicle proposal server 100. FIG. 11 is a diagram illustrating an example of a web page screen. 13 is a flowchart showing a flow of a vehicle suggestion process.

A preferred embodiment of the present invention will be described with reference to the attached drawings. In each drawing, the same reference numerals are used to denote the same or similar configurations.

A. System Overview of the Present Embodiment
FIG. 1 is an explanatory diagram showing an overview of a system 1000 according to this embodiment.
A user who has a vague image of a desired vehicle sends an idea for a vehicle to the vehicle proposal server 100 (step S1). When the vehicle proposal server 100 receives the idea for a vehicle, it refers to a database (described later) and identifies a vehicle model (e.g., SUV-type ◯×) that embodies the received idea. When the vehicle proposal server 100 identifies the vehicle model, it generates request information that includes the idea received from the proposing user and the vehicle model to be embodied. The vehicle proposal server 100 transmits the generated request information to a candidate for vehicle manufacturing.

Based on the request information, the vehicle manufacturer candidate generates proposal information that represents the vehicle manufacturing plan required to realize the idea (e.g., the required parts, delivery date, estimated cost, etc.) and transmits it to the vehicle proposal server 100 (step S2). The vehicle proposal server 100 posts the received proposal information on a specified web page (step S3).

Each potential customer understands the contents of the proposal information by accessing a specific web page. Each potential customer evaluates the customized vehicle shown in the proposal information and sends it as evaluation information to the vehicle proposal server 100 (step S4). When the vehicle proposal server 100 receives the evaluation information of the customized vehicle from each potential customer, it compiles it and outputs it to the outside (e.g., the vehicle manufacturer, etc.) (step S5).

With this system, only those vehicle ideas proposed by users that receive high praise from potential customers can be commercialized, making it possible to provide vehicles that meet customer demands at a realistic cost.

<System Configuration>
FIG. 2 is a diagram showing an example of the configuration of the system 1000.
The system 1000 includes a vehicle proposal server (information processing device) 100 and a terminal 200. The vehicle proposal server 100 and the terminal 200 are capable of communicating with each other via a network N.

One or more portions of network N may be wired or wireless. Network N may include, by way of example and without limitation, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), a portion of the Internet, a portion of the public switched telephone network (PSTN), a cellular network, Integrated Service Digital Networks (ISDNs), wireless LANs, Long Term Evolution (LTE), Code Division Multiple Access (CDMA), Bluetooth, satellite communications, or the like, or a combination of two or more thereof.

The vehicle proposal server 100 is, for example, configured by a server computer, and has functions such as using vehicle model information for each vehicle stored in an on-premise or cloud-based database (described later) to identify the vehicle model that embodies the vehicle-related idea proposed by the user, generating request information for vehicle manufacturer candidates, and posting proposal information received from vehicle manufacturer candidates on a web page (described in more detail later).

The terminal 200 is a terminal operated by a user, a vehicle manufacturing candidate, a potential customer, etc., and is configured as a personal computer, a handheld computing device, a smartphone, a mobile phone, a wearable terminal, etc.

A user operates the terminal 200 to generate ideas for a vehicle and transmit them to the vehicle proposal server 100. A potential vehicle manufacturer operates the terminal 200 to generate proposal information representing a vehicle manufacturing plan (e.g., required parts, delivery date, estimated cost, etc.) required to realize the proposed idea, and transmits the proposal information to the vehicle proposal server 100. A potential customer operates the terminal 200 to generate evaluation information for the customized vehicle indicated in the proposal information, and transmits the proposal information to the vehicle proposal server 100.

Note that the vehicle proposal server 100 and the terminal 200 described above do not necessarily have to be composed of a single computer, but may be composed of multiple computers and storage distributed over the network N.

<Hardware Configuration>
3 is a diagram showing an example of the hardware configuration of the vehicle proposal server 100 and the terminal 200. The vehicle proposal server 100 and the terminal 200 each have a CPU (Central Processing Unit) 1, a storage device 2 such as a ROM (Read Only Memory) or a RAM (Random Access Memory), a communication IF (Interface) 3 for wired or wireless communication, an input device 4 for accepting input operations, and an output device 5 for outputting information. The input device 4 is, for example, a keyboard, a mouse, a touch panel, a microphone, etc. The output device 5 is, for example, a display (screen) and/or a speaker, etc.

The following describes the functional configuration and functional overview of the vehicle proposal server 100 with reference to the drawings.

<Functional configuration and function overview>
FIG. 4 is a block diagram showing the functional configuration of the vehicle proposal server 100. As shown in FIG.

The vehicle proposal server 100 includes a collection unit 110 , a storage unit 120 , an identification unit 130 , a generation unit 140 , a transmission unit 150 , a reception unit 160 , an output unit 170 , and an evaluation unit 180 .
The collection unit 110, the identification unit 130, the generation unit 140, the transmission unit 150, the reception unit 160, the output unit 170, and the evaluation unit 180 are realized by the CPU 1 of the vehicle proposal server 100 executing various programs stored in the storage device 2. The programs can be stored in a storage medium such as a USB memory or a CD-ROM.

The collection unit 110 accepts vehicle-related ideas (image information, text information, audio information, etc.) proposed by users. Ideas related to vehicles include, for example, the installation of a roof tent or bed board, or the installation of parts that enable amphibious use. When the collection unit 110 accepts such ideas, it grasps the user's ideas by, for example, using AI (Artificial Intelligence) to perform image recognition, audio recognition, natural language processing, etc., and collects this as custom information for the vehicle desired by the user.

The memory unit 120 is realized by the storage device 2, and stores programs that realize the various functions of the vehicle proposal server 100, various data, etc. The memory unit 120 also includes a vehicle model database (DB) 121 that registers vehicle model information for each vehicle that can be selected by the vehicle proposal server 100, a customer database (DB) 122 that registers a potential customer list related to potential customers, and a manufacturer database (DB) 123 that registers a manufacturing candidate list related to manufacturing candidates.

Vehicle type information is, for example, information that indicates the type of vehicle that a vehicle manufacturer can provide, and may include not only information indicating the body type, such as sedan or minivan, but also information such as the year and grade.

A potential customer list is, for example, a list of customers held by a vehicle manufacturer. In the potential customer list, basic information about each customer (ID, name, age, gender, address, contact information, email address, SNS accounts, annual income, family composition, hobbies, etc.) and vehicle-related information about the vehicles owned by each customer (purchase history, repair history, vehicle name and model number, etc.) are registered for each customer.

The candidate manufacturer list is, for example, a list of manufacturers held by a vehicle manufacturer. The candidate manufacturer list includes basic information about each manufacturer (ID, company name, number of employees, address, contact information, email address, etc.) and performance information about the vehicle's manufacturing performance (manufacturing history, delivery date, cost, etc.) registered for each manufacturer.

Based on the vehicle idea (i.e., vehicle customization information) proposed by the user, the identification unit 130 identifies vehicle model information representing a vehicle manufacturing plan required to realize the idea from among multiple vehicle model information registered in the vehicle model DB 121. To explain by way of example, when the identification unit 130 determines, based on the vehicle customization information provided by the collection unit 110, that a roof tent is desired to be installed, it identifies vehicle model information (e.g., ◯ or ◯ for SUVs) of vehicles on which a roof tent can be installed as an option from among multiple vehicle model information registered in the vehicle model DB 121.

The generating unit 140 generates request information for having a manufacturing candidate create and propose a manufacturing plan in accordance with the vehicle model information and vehicle customization information of the vehicle identified by the identifying unit 130.
For example, if the vehicle customization information is "installation of a roof tent" and the vehicle model information is "SUV-type yes/no," the generation unit 140 generates request information that includes this information as well as other information necessary to realize the user's idea (such as parts, delivery date, and estimated cost) and that the request information should be proposed as a manufacturing proposal.

The sending unit 150 sends the request information generated by the generating unit 140 to the terminal 200 of the manufacturing candidate. The manufacturing candidate to which the request information is sent (i.e., the destination of the request information) may be set appropriately depending on the request content, etc. For example, the sending unit 150 selects the most suitable manufacturing candidate by comparing the request content indicated in the request information with the performance information of each manufacturing candidate registered in the manufacturing candidate list, and sends the request information to the selected manufacturing candidate. However, the selected manufacturing candidate is not limited to one company, and may be two or more companies (multiple companies).

The receiving unit 160 receives proposal information representing a manufacturing plan for a vehicle (i.e., a customized vehicle) that reflects the request information from the manufacturing candidate's terminal 200. The manufacturing plan generated by the manufacturing candidate includes information representing details of the customized vehicle (e.g., vehicle customization information, vehicle model information, required parts, delivery date, estimated cost, etc.).

The output unit 170 posts the proposal information received by the receiving unit 160 on a specified web page (e.g., the site of the vehicle proposal server 100).

FIG. 5 is a diagram showing an example of a screen P1 of a Web page on which proposal information is posted.
The web page screen P1 displays, for example, a completed image F1 of the customized vehicle, as well as vehicle customization information IF1, vehicle model information IF2, parts information IF3 regarding required parts, delivery date information IF4 regarding delivery dates, and cost information IF5 regarding predicted costs.

Returning to FIG. 4, the evaluation unit 180 compiles evaluations of the customized vehicle by potential customers and outputs them to the outside (e.g., the manufacturer). In more detail, the evaluation unit 180 refers to the proposal information and the potential customer list, and identifies potential customers who are likely to be interested in the customized vehicle shown in the proposal information. For example, in the case of a customized vehicle equipped with a "roof tent" or the like, the evaluation unit 180 extracts potential customers who are likely to be interested in outdoor sports, camping, etc. from the customer DB 122, and requests the terminal 200 of the extracted potential customer to evaluate the customized vehicle.

Although the number of potential customers requesting an evaluation is not important, in the following, two or more potential customers are assumed (see FIG. 1). When the potential customer receives such a request, the potential customer operates the terminal 200 appropriately to access the web page and understand the contents of the proposed information (i.e., details of the customized vehicle, etc.). The potential customer then inputs evaluation information of the customized vehicle into the terminal 200. To explain by way of example, the potential customer inputs information such as whether or not he/she intends to purchase the customized vehicle, and requests regarding the customized vehicle, as evaluation information of the customized vehicle. The terminal 200 of the potential customer transmits the input evaluation information of the customized vehicle to the vehicle proposal server 100. When the evaluation unit 180 receives evaluation information of the customized vehicle from the terminal 200 of each potential customer, it compiles the information and outputs it to the vehicle manufacturer, etc. The vehicle manufacturer manufactures the customized vehicle based on the evaluation information obtained from the evaluation unit 180 when a predetermined condition is met (for example, when a certain number of purchases or more are expected).

The evaluation unit 180 may provide the vehicle manufacturer with evaluation information on the customized vehicle using graphs, tables, etc. The operation of the vehicle proposal server 100 will be described below with reference to the drawings.

<Operation>
FIG. 6 is a flowchart showing the flow of the vehicle proposal process executed by the vehicle proposal server 100.
When the collection unit 110 receives vehicle-related ideas proposed by a user, it uses AI to understand the user's ideas and collects them as customization information for the vehicle desired by the user (step Sa1).
The identification unit 130 identifies vehicle model information of a vehicle required to realize the idea from among a plurality of vehicle model information registered in the vehicle model DB 121 based on the vehicle customization information (step Sa2).

The generating unit 140 generates request information for the manufacturing candidate to create and propose a manufacturing plan according to the vehicle model information and vehicle customization information identified by the identifying unit 130 (step Sa3).

The transmitting unit 150 transmits the request information generated by the generating unit 140 to the manufacturing candidate's terminal 200 (step Sa4).

The receiving unit 160 receives proposal information representing a manufacturing plan for a customized vehicle that reflects the request information, sent from the manufacturing candidate's terminal 200 (step Sa5).

The output unit 170 posts the proposal information received by the receiving unit 160 on a specified web page (step Sa6).

The evaluation unit 180 refers to the proposal information and the potential customer list, and identifies potential customers who may be interested in the customized vehicle shown in the proposal information (step Sa7).

The evaluation unit 180 requests the terminal 200 of the identified potential customer to evaluate the customized vehicle (step Sa8).
When the evaluation unit 180 receives the evaluation information of the customized vehicle from the terminal 200 of the potential customer, it compiles the information and outputs it to an external party such as the manufacturer (step Sa9), and the process ends.

C. Modifications The present invention is not limited to the above-described embodiment, and can be implemented in various other forms without departing from the scope of the present invention. Therefore, the above-described embodiment is merely an example in all respects and should not be interpreted as being restrictive. For example, the order of each of the above-described processing steps can be arbitrarily changed or executed in parallel as long as no contradiction occurs in the processing content.

In addition, in the above embodiment, customers who are likely to be interested in customized vehicles are identified as potential customers by referring to the proposal information and the potential customer list, but the present invention is not limited to this. For example, customers randomly selected from the potential customer list may be identified as potential customers.

In addition, in the above embodiment, a four-wheeled automobile is used as an example of a vehicle, but this is not intended to be limiting, and the invention can be applied to a variety of vehicles with wheels. Furthermore, the invention can be applied to any moving object, including not only vehicles, but also ships, airplanes, rockets, etc.

In addition, in this specification, a "unit" does not simply mean a physical configuration, but also includes cases where the processing performed by the "unit" is realized by software. Furthermore, the processing performed by one "unit" or device may be realized by two or more physical configurations or devices, and the processing performed by two or more "units" or devices may be realized by one physical means or device.

1000...system, 100...vehicle proposal server, 110...collection unit, 120...storage unit, 121...vehicle model database, 122...customer database, 123...manufacturer database, 130...identification unit, 140...generation unit, 150...transmission unit, 160...reception unit, 170...output unit, 180...evaluation unit, 200...terminal, F1...image of completed model, IF1...vehicle customization information, IF2...vehicle model information, IF3...parts information, IF4...delivery date information, IF5...cost information.

Claims (1)

A collection unit that collects custom information of a vehicle desired by a user;
A database that contains information on the vehicle models that can be selected,
A potential customer list that includes vehicle-related information about the vehicles owned by each customer;
an identification unit that identifies vehicle model information required to realize the user's desire from among a plurality of vehicle model information registered in the database based on the custom information;
A generation unit that generates request information based on the specified vehicle type information and the specified custom information;
a transmission unit that transmits the generated request information to a manufacturing candidate;
a receiving unit that receives, from the manufacturing candidate, proposal information of a customized vehicle that reflects the request information;
an output unit that outputs the received proposal information ;
an evaluation unit that identifies a potential customer of the customized vehicle that reflects the request information based on the proposal information and the potential customer list, and requests a terminal of the identified potential customer of the customized vehicle to evaluate the customized vehicle;
The evaluation unit is an information processing device that receives evaluation information indicating an evaluation of the customized vehicle from a terminal of the potential customer and outputs the evaluation information to a vehicle manufacturer .

Images