Support system and support device

Abstract

To provide a support system capable of efficiently proposing building and exterior specifications that meet client's wishes to clients.SOLUTION: The support system (SY) of the present invention for assisting a proposer in suggesting at least one of specifications of a building and exterior to a client is provided with a control unit for accessing, based on a request from the proposer, a database storing material data related to building materials and / or exterior materials; extracting material data selected by the proposer from the stored material data; generating material catalog data (such as building material catalog data) including the extracted material data; and based on a request from the client, providing the generated material catalog data to the client.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a technique for supporting a proposer who proposes specifications for a building or exterior structure to a client. [Background technology]

[0002] Patent Document 1 discloses technology related to a system that reduces the burden on builders in creating estimates. Patent Document 2 discloses technology related to a system that allows for easy search of building design information. Patent Document 3 discloses technology related to a system that advances various construction tasks with the approval of the client, supervisor, and builder. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2023-056227 [Patent Document 2] Japanese Patent Publication No. 2022-121585 [Patent Document 3] Japanese Patent Application Laid-Open No. 2009-134685 Summary of the Invention [Problem to be solved by the invention]

[0004] There has long been a demand for a system that can efficiently propose building and exterior specifications to clients that meet their needs.

[0005] The present invention has been made in consideration of the above points, and its purpose is to provide a system that can efficiently propose to a client specifications for a building or exterior that meet the client's wishes. [Means for solving the problem]

[0006] As a solution to achieve the above objectives, The support system of the present invention comprises: A support system for supporting a proposer who proposes specifications of at least one of a building and an exterior structure to a client, A control unit is provided, accessing a database storing material data related to building materials and / or exterior materials based on a request from the proposer, extracting material data selected by the proposer from the stored material data, and generating material catalog data including the extracted material data; Based on a request from the client, the material catalog data generated by the control unit is provided to the client. It is characterized by:

[0007] In addition, the control unit accessing a database storing sample data relating to building samples and / or exterior structure samples based on a request from the proposer, extracting sample data selected by the proposer from the stored sample data, and generating sample catalog data including the extracted sample data; The sample catalog data generated by the control unit is provided to the client based on a request from the client. This may be done.

[0008] In addition, the control unit When storing client data relating to the client in a database based on a request from the proposer, generating a URL corresponding to the client and sending the generated URL to an email address used by the client corresponding to the URL; The catalog data generated by the control unit and the sample catalog data are provided to the client based on the URL specified by the client. This may be done.

[0009] As a solution to achieve the above objectives, The support device of the present invention comprises: A support device that supports a proposer who proposes specifications of at least one of a building and an exterior structure to a client, A control unit is provided, The control unit accessing a database storing material data related to building materials and / or exterior materials based on a request from the proposer, extracting material data selected by the proposer from the stored material data, and generating material catalog data including the extracted material data; Based on a request from the client, the material catalog data generated by the control unit is provided to the client. It is characterized by:

[0010] In addition, the control unit The control unit accessing a database storing sample data relating to building samples and / or exterior structure samples based on a request from the proposer, extracting sample data selected by the proposer from the stored sample data, and generating sample catalog data including the extracted sample data; The sample catalog data generated by the control unit is provided to the client based on a request from the client. This may be done.

[0011] In addition, the control unit When storing client data relating to the client in a database based on a request from the proposer, generating a URL corresponding to the client and sending the generated URL to an email address used by the client corresponding to the URL; The catalog data generated by the control unit and the sample catalog data are provided to the client based on the URL specified by the client. This may be done. [Effects of the Invention]

[0012] The present invention can efficiently propose to a client specifications for a building or exterior that meet the client's wishes. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is an explanatory diagram for explaining an overview of a first embodiment of the present invention. [Figure 2] 1 is a schematic diagram showing a system configuration according to a first embodiment. [Figure 3] FIG. 2 is a block diagram showing the hardware configuration of a server according to the first embodiment. [Figure 4] FIG. 2 is a diagram schematically illustrating data stored in a database according to the first embodiment. [Figure 5] FIG. 2 is a diagram schematically illustrating data stored in a database according to the first embodiment. [Figure 6] FIG. 2 is a diagram schematically illustrating data stored in a database according to the first embodiment. [Figure 7] 4 is a flowchart showing part of the processing in the system according to the first embodiment. [Figure 8] 4 is a flowchart showing part of the processing in the system according to the first embodiment. [Figure 9] FIG. 2 is a diagram schematically illustrating an example of a screen according to the first embodiment. [Figure 10] FIG. 2 is a diagram schematically illustrating an example of a screen according to the first embodiment. [Figure 11] 4 is a flowchart showing part of the processing in the system according to the first embodiment. [Figure 12] 4 is a flowchart showing a building materials catalog generation process according to the first embodiment. [Figure 13] FIG. 2 is a diagram schematically illustrating an example of a screen according to the first embodiment. [Figure 14] 4 is a flowchart showing part of the processing in the system according to the first embodiment. [Figure 15] 4 is a flowchart showing part of the processing in the system according to the first embodiment. [Figure 16] 10 is a flowchart showing a process of client registration etc. according to the first embodiment. [Figure 17] 4 is a flowchart showing part of the processing in the system according to the first embodiment. [Figure 18] 10 is a flowchart showing a building materials catalog linking process according to the first embodiment. [Figure 19] 4 is a flowchart showing part of the processing in the system according to the first embodiment. [Figure 20] 10 is a flowchart showing a process for providing a catalog of building materials, etc. according to the first embodiment. [Figure 21] FIG. 2 is a diagram schematically illustrating an example of a screen according to the first embodiment. [Figure 22] FIG. 2 is a diagram schematically illustrating an example of a screen according to the first embodiment. [Figure 23] FIG. 10 is an explanatory diagram for explaining an overview of a second embodiment of the present invention. [Figure 24] FIG. 10 is a block diagram showing the hardware configuration of a server according to a second embodiment. [Figure 25] FIG. 10 is a diagram schematically illustrating data stored in a database according to the second embodiment. [Figure 26] FIG. 10 is a diagram schematically illustrating data stored in a database according to the second embodiment. [Figure 27] FIG. 10 is a diagram schematically illustrating data stored in a database according to the second embodiment. [Figure 28] 10 is a flowchart showing part of the processing in the system according to the second embodiment. [Figure 29] 10 is a flowchart showing part of the processing in the system according to the second embodiment. [Figure 30] 10 is a flowchart showing a process for generating a sample catalog of buildings, etc. according to the second embodiment. [Figure 31] 10 is a flowchart showing part of the processing in the system according to the second embodiment. [Figure 32] 10 is a flowchart showing a sample catalog linking process for buildings, etc. according to the second embodiment. [Figure 33] 10 is a flowchart showing part of the processing in the system according to the second embodiment. [Figure 34]10 is a flowchart showing a process for providing a sample catalog of buildings, etc. according to the second embodiment. [Figure 35] FIG. 10 is a diagram schematically illustrating an example of a screen according to the second embodiment. [Figure 36] FIG. 10 is a diagram schematically illustrating an example of a screen according to the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0014] A first embodiment of the present invention will be described below with reference to the drawings.

[0015] FIG. 1 is an explanatory diagram for explaining an overview of the first embodiment.

[0016] The client shown in Figure 1 is a person who wishes to, considers, or plans the construction, renovation, remodeling, or repair of a building, or the construction or installation of a new exterior structure. The client is, for example, an individual who is planning to build a new residence for themselves.

[0017] The exterior is what we call the exterior, and includes gates and doors (gates), hedges, fences, garages, garden equipment, etc. around the building.

[0018] The proposer shown in Figure 1 is a person who proposes specifications for at least one of the building and the exterior to a client. For example, the proposer proposes materials as specifications for the building and the exterior to a client who wishes to build a new building and carry out exterior construction work on that building.

[0019] Examples of building materials and exterior construction materials include gates, copings (horizontal beams placed over gates, etc.), entrance arches, doors, lighting, mailboxes, delivery boxes, nameplates, locks, intercoms, fences, coping stones (stones placed over fences, etc.), handrails, fences, garages, garden equipment (plants, garden trees, artificial ponds, etc.), balconies, windows, wallpaper, etc. Building materials and exterior construction materials broadly include building materials and building accessories.

[0020] Proposers include, for example, house manufacturers, construction companies, developers, housing sales agencies, housing sales agents, building design offices, and construction management offices, and also include a wide range of corporations and individual business owners related to construction.

[0021] In the following explanation, buildings and exterior structures are collectively referred to as "buildings, etc." Furthermore, building materials and exterior structure materials are collectively referred to as "building materials, etc."

[0022] Before holding a meeting with a client regarding the specifications of a building, etc., the proposer selects building materials, etc. that suit the client's preferences and the current situation from among building materials, etc. that are available on the market, and proposes the selected building materials, etc. to the client.

[0023] In the first embodiment, as shown in FIG. 1, the proposer uses the system SY to create materials related to building materials, etc. to be proposed to the client (hereinafter referred to as the "building materials, etc. catalog"), and the client uses the system SY to be able to view the building materials, etc. catalog created by the proposer before holding a meeting with the proposer.

[0024] As will be described in more detail later, System SY is equipped with a building materials database for storing (accumulating) data related to building materials, etc. (hereinafter referred to as "building materials data"). Proposers can use the building materials database to create a building materials catalog.

[0025] In addition, the system SY is equipped with a building materials catalog database for storing (accumulating) data related to building materials catalogs (hereinafter referred to as "building materials catalog data"). The proposer can store the building materials catalogs he or she has created in the building materials catalog database. The requester can then view the building materials catalogs stored in the building materials catalog database via the system SY.

[0026] The storer shown in Figure 1 is the person who stores building material data in the building material database. Storers include, for example, building material manufacturers that manufacture, sell, and develop building materials, administrators who manage the system SY, and those who assist the administrators.

[0027] FIG. 2 is a schematic diagram showing the configuration of the system SY according to the first embodiment.

[0028] The system SY includes a proposer terminal 1, a requester terminal 2, a storer terminal 3, and a server (information processing device) 4.

[0029] The proposer terminal 1 is a communication terminal (for example, a personal computer) used by the proposer. The proposer terminal 1 is connected to the network N. The proposer terminal 1 is connected to the server 4 via an ID (account) or the like that identifies the proposer.

[0030] The proposer terminal 1 has an input device (for example, a keyboard or a mouse) and an output device (for example, a display). The output device of the proposer terminal 1 has a display area 1a that displays a predetermined screen (image).

[0031] The requester terminal 2 is a communication terminal (for example, a personal computer) used by the requester. The requester terminal 2 is connected to the network N. The requester terminal 2 is connected to the server 4 via a predetermined URL (uniform resource locator). The predetermined URL is the URL of a web page that displays catalog data of building materials, etc., and is used to specify the catalog data of building materials, etc. The requester terminal 2 may also be configured to connect to the server 4 via an ID (account) or the like that identifies the requester.

[0032] The requester terminal 2 has an input device (for example, a keyboard or a mouse) and an output device (for example, a display). The output device of the requester terminal 2 has a display area 2a for displaying a predetermined image (screen).

[0033] The storage user terminal 3 is a communication terminal (for example, a personal computer) used by the storage user. The storage user terminal 3 is connected to the network N. The storage user terminal 3 is connected to the server 4 via an ID (account) or the like that identifies the storage user.

[0034] The storer terminal 3 has an input device (for example, a keyboard or a mouse) and an output device (for example, a display). The output device of the storer terminal 3 has a display area 3a for displaying a predetermined image (screen).

[0035] The server 4 is an information processing device that processes information transmitted from the proposer terminal 1, the requester terminal 2, and the storage terminal 3. The server 4 functions as a platform required to operate the system SY. Programs for performing various processes are installed on the server 4. The server 4 is connected to the proposer terminal 1, the requester terminal 2, and the storage terminal 3 via the network N. The server 4 is constructed, for example, in the cloud.

[0036] FIG. 3 is a block diagram showing the hardware configuration of the server 4. As shown in FIG.

[0037] The server 4 includes a storage unit 20 and a control unit 30. The storage unit 20 and the control unit 30 are electrically connected via a communication bus (not shown).

[0038] The storage unit 20 includes a ROM, a RAM, and a hard disk (not shown). The storage unit 20 stores programs executed by the control unit 30. The storage unit 20 includes a building materials database (hereinafter referred to as "building materials DB"), a building materials catalog database (hereinafter referred to as "building materials catalog DB"), and a requester database (hereinafter referred to as "requester DB").

[0039] In the first embodiment, the server 4 is configured to include a building materials DB, a building materials catalog DB, and a requester DB, but this configuration is not limited to this, and it is sufficient that the system SY is equipped with a building materials DB, a building materials catalog DB, and a requester DB, and a separate device connectable to a network N different from the server 4 may be configured to include the building materials DB, the building materials catalog DB, and the requester DB.

[0040] The building materials DB stores data on building materials.

[0041] Building materials data includes image and video data relating to the design of building materials (shape, pattern, color composition) (hereinafter referred to as "building materials image data"), data relating to the category to which building materials belong (hereinafter referred to as "building materials category data"), data on manufacturers that provide building materials to the market (hereinafter referred to as "building materials manufacturer data"), data on the product name and serial number of building materials (hereinafter referred to as "building materials name data"), data on dimensions such as height and width, color, weight, material, durability, etc. of building materials (hereinafter referred to as "building materials specification data"), data on the price of building materials (hereinafter referred to as "building materials price data"), and other data.

[0042] The building materials DB stores building materials image data, building materials category data, building materials manufacturer data, building materials name data, building materials specification data, building materials price data, and other data, each linked to an ID (hereinafter referred to as a "building materials ID"), which is an identifier that identifies the building materials.

[0043] FIG. 4 is a diagram for explaining an example of building materials data stored in the building materials DB.

[0044] In Figure 4, for example, the building materials data for gate a1, which is associated with building materials ID 001, the building materials data for gate a2, which is associated with building materials ID 002, the building materials data for gate a3, which is associated with building materials ID 003, and the building materials data for gate a4, which is associated with building materials ID 004, are stored in the building materials DB.

[0045] As shown in Figure 4, for example, building material id001 is linked to gate a1 (building material name data), image a1 of gate a1 (building material image data), gate (building material category data), building material manufacturer A (building material manufacturer data), height 100 cm (building material specification data), and 200,000 yen (building material price data). It goes without saying that instead of image a1, video a1 of gate a1 may be linked to building material id001.

[0046] The building materials catalog DB stores catalog data of building materials.

[0047] The building materials catalog DB stores an ID (hereinafter referred to as the "building materials catalog ID") that identifies the building materials catalog data, data relating to the name of the building materials catalog (hereinafter referred to as the "building materials catalog name data"), and a building materials ID associated with the building materials listed in the building materials catalog (the building materials data that constitute the building materials catalog data).

[0048] In the first embodiment, the name of the building materials catalog (hereinafter referred to as the "building materials catalog name") is configured to be determined by the control unit 30. As will be described in detail later, the control unit 30 determines the building materials catalog name when storing building materials catalog data in the building materials catalog DB. The building materials catalog name is a combination of numbers, hiragana, katakana, kanji, European letters (uppercase and lowercase), symbols, etc.

[0049] FIG. 5 is a diagram for explaining an example of catalog data of building materials, etc. stored in the building materials, etc. catalog DB.

[0050] 5, for example, Gate Catalog 1 (building materials catalog name data), Building Materials ID 001, and Building Materials ID 003 are stored in a linked state in Building Materials Catalog ID 001. In other words, Gate Catalog 1 is a catalog that lists the building materials corresponding to Building Materials ID 001 and the building materials corresponding to Building Materials ID 003.

[0051] The requester DB stores data relating to requesters (hereinafter referred to as "requester data").

[0052] FIG. 6 is a diagram illustrating an example of requester data stored in the requester DB.

[0053] The requester DB stores an ID (hereinafter referred to as the "requester ID") that identifies the requester data, data related to the requester's name (hereinafter referred to as the "requester name data"), the email address used by the requester (hereinafter referred to as the "requester email address"), a URL for specifying the building materials catalog data that the requester can view, and the building materials catalog ID corresponding to the building materials catalog data that the requester can view, all linked together.

[0054] The control unit 30 includes a CPU, a ROM, and a RAM (not shown). The control unit 30 reads out programs stored in the storage unit 20 and loads them into the RAM to execute various processes.

[0055] Next, a description will be given of each process performed by the control unit 30. In the following description, it is assumed that the proposer terminal 1 and the storage terminal 3 are each connected to the server 4 via an ID.

[0056] FIG. 7 is a flowchart showing the process executed between the storage terminal 3 and the server 4.

[0057] 7 includes a process of storing building material data in the building material DB. As shown in the figure, the control unit 30 executes a building material data storage process to store the building material data transmitted from the storer terminal 3 to the server 4 in the building material DB based on a request from the storer who stores the building material data in the building material DB (step S10).

[0058] Although not shown in the figure, the control unit 30, when it receives building materials data sent from the storage user terminal 3 to the server 4, generates a building materials ID corresponding to the received building materials data, links the received building materials data to this generated building materials ID, and stores it in the building materials DB.

[0059] For example, when server 4 receives building materials data related to gate a1 (see Figure 4), it generates building materials ID001 corresponding to gate a1, and links gate a1 (building materials name data), image a1 of gate a1 (building materials image data), gate (building materials category data), building materials manufacturer A (building materials manufacturer data), height 100 cm (building materials specification data), and 200,000 yen (building materials price data) to this generated building materials ID001 and stores them in the building materials DB.

[0060] FIG. 8 is a flowchart showing the processing executed between the proposer terminal 1 and the server 4.

[0061] The process shown in Fig. 8 includes a process for viewing building materials data stored in the building materials DB. As shown in the figure, the control unit 30 accesses the building materials DB based on a viewing request from a proposer who wishes to view the building materials data stored in the building materials DB, extracts the building materials data stored in the building materials DB, and transmits the extracted building materials data to the proposer terminal 1 (step S20). Upon receiving the building materials data transmitted from the control unit 30, the proposer terminal 1 displays the received building materials data in the display area 1a of the proposer terminal 1 (step S30).

[0062] FIG. 9 is a diagram schematically illustrating an example of a screen G1 displayed in the display area 1a of the proposer terminal 1 in step S20.

[0063] 9 shows an example of a screen G1 that displays data on building materials, etc., belonging to the gate category among the data on building materials, etc., stored in the building materials, etc. DB. As shown in the figure, the screen G1 includes information on the category to which the building materials, etc., belong (in the example shown in the figure, text information on gates located in the upper left of the screen G1), multiple identification signs G1a, and a building materials, etc. catalog generation button G1b.

[0064] The identification mark G1a is rectangular. Each identification mark G1a includes one building material image data and all or part of the building material data (e.g., building material specification data) corresponding to the building material image data. In the example of FIG. 9, the building material image data is omitted from the identification mark G1a, but each of the four identification marks G1a includes one of the building material image data for gate a1, gate a2, gate a3, and gate a4.

[0065] In the first embodiment, the proposer can create a catalog of building materials, etc. to propose to the client via the screen G1 shown in Fig. 9. More specifically, the proposer can create the catalog of building materials, etc. by selecting an identification mark G1a including image data of building materials, etc. related to the building materials, etc. that the proposer wants to propose to the client, according to the client's preferences, etc. The building materials, etc. catalog generation button G1b is a button for requesting the server 4 to generate a building materials, etc. catalog.

[0066] Figure 10 is a screen G1 showing an example in which the proposer selects an identification sign G1a containing image data of building materials, etc. related to gate a1 and an identification sign G1a containing image data of building materials, etc. related to gate a4.

[0067] FIG. 11 is a flowchart showing the processing executed between the proposer terminal 1 and the server 4.

[0068] 11 includes a process for generating a building materials catalog. The proposer terminal 1 transmits information on the identification marker G1a selected by the proposer to the server 4 based on an operation of selecting the building materials catalog generation button G1b (a request to generate a building materials catalog) (step S40). When the control unit 30 receives the information on the identification marker G1a transmitted from the proposer terminal 1, it executes a process for generating building materials catalog data (building materials catalog generation process) (step S50).

[0069] FIG. 12 is a flowchart showing the building materials catalog generation process (step S50).

[0070] As shown in FIG. 12, first, the control unit 30 refers to the building materials DB to identify the building materials data corresponding to the information of the identification label G1a received in step S50 (step S51). Next, the control unit 30 identifies the building materials ID associated with the building materials data identified in step S51 (step S52). Next, the control unit 30 generates a building materials catalog ID (step S53). Next, the control unit 30 generates a building materials catalog name corresponding to the building materials catalog ID generated in step S53 (step S54). Note that when generating the building materials catalog name in step S54, the control unit 30 generates a building materials catalog name that is different from the building materials catalog name stored in the building materials catalog DB. Finally, the control unit 30 links the building materials catalog ID generated in step S53 with the building materials catalog ID identified in step S52 and the building materials catalog name generated in step S54, stores these in the building materials catalog DB (step S55), and terminates the building materials catalog generation process.

[0071] For example, assume that information on the identification label G1a corresponding to gate a1 and information on the identification label G1a corresponding to gate a4 are received in step S50. In this case, the control unit 30 refers to the building materials DB (see FIG. 4) in step S51 to identify building materials ID001 corresponding to gate a1 and building materials ID004 corresponding to gate a4, generates building materials catalog ID003 in step S53 (see FIG. 5), generates gate catalog 3 (building materials catalog name) in step S54 (see FIG. 5), and links building materials ID001, building materials ID004, and gate catalog 3 to building materials catalog ID003 and stores them in the building materials catalog DB (see FIG. 5).

[0072] In the first embodiment, as shown in step S30 of FIG. 8, in response to a request to view building materials data, the screen G1 shown in FIG. 9 is displayed in the display area 1a of the proposer terminal 1. However, the present invention is not limited to this configuration. In order to make it easier to search for building materials data, in response to a request to view building materials data, the screen G2 shown in FIG. 13 may be displayed, for example, in which the building materials data stored in the building materials DB is sorted, for example, by the category to which the building materials belong, or by the manufacturer of the building materials, and when the proposer selects the gate button G2a on this screen G2, the screen G1 shown in FIG. 9 is displayed in the display area 1a.

[0073] In the first embodiment, in step S54 (FIG. 12) of the building materials catalog generation process, the control unit 30 generates a building materials catalog name and stores this generated building materials catalog name in the building materials catalog DB, but the configuration is not limited to this, and a configuration may also be adopted in which the proposer formulates a building materials catalog name, transmits this formulated building materials catalog name to the server 4 via the proposer terminal 1, and stores this transmitted building materials catalog name in the building materials catalog DB. In short, a configuration in which the proposer assigns a building materials catalog name may also be adopted.

[0074] FIG. 14 is a flowchart showing the processing executed between the proposer terminal 1 and the server 4.

[0075] 14 includes a process for viewing requester data stored in the requester DB. As shown in the figure, the control unit 30 accesses the requester DB based on a viewing request from a requester who wishes to view the requester data, extracts the requester data stored in the requester DB, and transmits the extracted requester data to the proposer terminal 1 (step S60). Upon receiving the requester data transmitted from the server 4, the proposer terminal 1 displays the received requester data in the display area 1a of the proposer terminal 1 (step S70).

[0076] FIG. 15 is a flowchart showing the processing executed between the proposer terminal 1 and the server 4.

[0077] 15 includes a process of registering (storing) requester data (new requester data not stored in the requester DB) in the requester DB. As shown in the figure, the proposer terminal 1 transmits requester name data and a requester email address, which are part of the requester data, to the server 4 based on a registration request from the proposer to register a new requester in the requester DB (step S80). Upon receiving the requester name data and the requester email address transmitted from the proposer terminal 1, the control unit 30 executes a process of registering the received data in the requester DB (requester registration process, etc.) (step S90).

[0078] FIG. 16 is a flowchart showing the requester registration process (step S90).

[0079] First, the control unit 30 generates a requester ID corresponding to the requester name data received in step S90 (step S91). Next, the control unit 30 generates a URL corresponding to the requester name data received in step S90 (step S92). Next, the control unit 30 associates the requester ID generated in step S91 with the requester name data and requester email address received in step S90 and the URL generated in step S92, and stores these in the requester DB (step S93). Finally, the control unit 30 sends the URL generated in step S92 (the URL stored in the requester DB in step S93) to the requester email address received in step S90 (the requester email address stored in the requester DB in step S93) (step S94), and ends the requester registration process, etc.

[0080] In the first embodiment, a URL corresponding to the requester data is generated in step S92 of the requester registration process shown in Fig. 16. The URL generated in step S92 is a URL related to a web page for displaying the building materials catalog data stored in the building materials catalog DB in the display area 2a of the requester terminal 2, and is used to specify the building materials catalog data created by the proposer for the requester.

[0081] FIG. 17 is a flowchart showing the processing executed between the proposer terminal 1 and the server 4.

[0082] 17 includes a process of linking the requester data stored in the requester DB with the building materials catalog data stored in the building materials catalog DB (in other words, a process of providing the requester with a building materials catalog created by the proposer for the requester). As shown in the figure, the control unit 30 accesses the requester DB based on a request from the proposer to view the requester data stored in the requester DB, and transmits the requester data stored in the requester DB to the proposer terminal 1 (step S100). Upon receiving the requester data transmitted from the server 4, the proposer terminal 1 displays the received requester data in the display area 1a of the proposer terminal 1 (step S110).

[0083] The proposer can use the input device of the proposer terminal 1 to select the requester data corresponding to the requester to whom he / she wishes to provide building materials catalog data from the requester data displayed in the display area 1a of the proposer terminal 1 in step S110.

[0084] The proposer terminal 1 transmits the requester data selected by the proposer to the server 4 based on the operation of the proposer (step S120). Based on receiving the requester data transmitted from the proposer terminal 1, the control unit 30 temporarily stores the received requester data in the storage unit 20, and also accesses the building materials etc. catalog DB and transmits the building materials etc. catalog data stored in the building materials etc. catalog DB to the proposer terminal 1 (step S130). Based on receiving the building materials etc. catalog data transmitted from the control unit 30, the proposer terminal 1 displays the received building materials etc. catalog data in the display area 1a of the proposer terminal 1 (step S140).

[0085] The proposer can use the input device of the proposer terminal 1 to select the building materials, etc. catalog data that the proposer wishes to provide to the client (client data sent to server 4) selected by the proposer in step S120 from the building materials, etc. catalog data displayed in the display area 1a of the proposer terminal 1 in step S140.

[0086] The proposer terminal 1 transmits the building materials catalog data selected by the proposer to the server 4 based on the operation of the proposer (step S150). Based on receiving the building materials catalog data transmitted from the proposer terminal 1, the control unit 30 executes a process of linking the client data with the building materials catalog data (building materials catalog linking process) (step S160).

[0087] FIG. 18 is a flowchart showing the building materials catalog linking process (step S160).

[0088] First, the control unit 30 refers to the requester DB to identify the requester ID associated with the requester data temporarily stored in step S130 (step S161). Next, the control unit 30 refers to the building materials catalog DB to identify the building materials catalog ID associated with the building materials catalog data received in step S160 (step S162). Finally, the control unit 30 links the requester ID identified in step S161 with the building materials catalog ID identified in step S162 (step S163), and ends the building materials catalog linking process.

[0089] For example, assume that requester ID001 is identified in step S161, and building materials catalog ID003 is identified in step S162. In this case, the control unit 30 links requester ID001 with building materials catalog ID003 (see FIG. 6). That is, in this example, the proposer causes the control unit 30 to execute a process of linking requester ID001 with building materials catalog ID003 in order to provide gate catalog 3 to requester Y1.

[0090] In the first embodiment, as shown in Figure 6, the client ID 001 stored in the client DB is linked to the building materials catalog ID 003, but this configuration is not limited to this as long as the client ID 001 and the building materials catalog ID 003 are linked.For example, the configuration may be such that the client ID 001 is linked to the building materials catalog ID 003 (see Figure 5) stored in the building materials catalog DB, or a separate database may be set up and information linking the client ID 001 and the building materials catalog ID 003 stored in that database.

[0091] FIG. 19 is a flowchart showing the process executed between the client terminal 2 and the server 4.

[0092] The process shown in Fig. 19 includes a process in which a requester browses building materials catalog data. As shown in the figure, the requester terminal 2 requests the server 4 to browse the building materials catalog (step S170) based on the requester's operation of specifying a URL (see step S94 in Fig. 16; hereinafter, also referred to as the "issued URL") sent to the email address used by the requester. Upon receiving the request to browse the building materials catalog from the requester, the control unit 30 executes a process (building materials catalog provision process) to provide the building materials catalog data to the requester (step S180).

[0093] FIG. 20 is a flowchart showing the process of providing a catalog of building materials, etc. (step S180).

[0094] First, the control unit 30 refers to the requester DB to identify the building materials catalog ID corresponding to the URL specified in step S170 (step S181). Next, the control unit 30 refers to the building materials catalog DB to identify the building materials ID linked to the building materials catalog ID specified in step S181 (step S182). Next, the control unit 30 refers to the building materials DB to identify the building materials data corresponding to the building materials ID specified in step S182 (step S183). Next, the control unit 30 extracts the building materials data specified in step S183 from the building materials DB (step S184). Finally, the control unit 30 transmits the building materials data extracted in step S184 to the requester terminal 2 that specified the URL (step S185), and ends the building materials catalog provision process.

[0095] For example, suppose that in step S170, the requester Y1 specifies the URL issued to the requester Y1 using the requester terminal 2. In this case, in step S181, the control unit 30 identifies the building materials catalog ID003 associated with the requester ID001 (see FIG. 6), in step S182, refers to the building materials catalog DB to identify the building materials ID001 and ID004 linked to the building materials catalog ID003 (see FIG. 5), in step S183, refers to the building materials DB to identify the building materials data related to gate a1 and gate a4 corresponding to the building materials ID001 and ID004 (see FIG. 4), in step S184, extracts the building materials data related to gate a1 and gate a4, and finally, in step S185, transmits the building materials data related to gate a1 and gate a4 to the requester terminal 2 used by the requester Y1.

[0096] Returning to the explanation of Figure 19, upon receiving the building materials data etc. sent from the control unit 30, the client terminal 2 displays the received building materials data etc. in the display area 2a of the client terminal 2 (step S190).

[0097] Fig. 21 is a diagram showing an example of screen G3. More specifically, this is a screen showing an example of building materials data displayed in the display area 2a of the client terminal 2 in step S190 of Fig. 19.

[0098] As shown in Figure 21, screen G3 includes an area G3a that displays building material data related to gate a1, and an area G3b that displays building material data related to gate a4. Above areas G3a and G3b, manufacturer data for the corresponding building materials is displayed. Area G3a includes arrows G3a1 and G3a2. Area G3b includes arrows G3b1 and G3b2. Arrows G3a1, G3a2, G3b1, and G3b2 are used to change the building material data displayed in the corresponding areas G3a and G3b.

[0099] The requester terminal 2 changes the building material data, etc. related to the gate a1 displayed in the area G3a each time the requester performs an operation to select, for example, the arrows G3a1 and G3a2 included in the area G3a. For example, when the image a1 of the gate a1 is displayed in the area G3a and the requester performs an operation to select the arrow G3a1 once, a height of 100 cm (standard data on building materials, etc.) is displayed in the area G3a, and when the height of 100 cm (standard data on building materials, etc.) is displayed in the area G3a and the requester performs an operation to select the arrow G3a2 once, the image a1 of the gate a1 is displayed in the area G3a.

[0100] In the first embodiment, the display area 2a of the requester terminal 2 is configured to display the building materials data (e.g., FIG. 21) proposed by the proposer based on the requester's operation of specifying a URL in step S170 of FIG. 19 (step S190). However, this configuration is not limited to this. For example, based on the requester's operation of specifying a URL, first, a screen G4 (FIG. 22) dedicated to the requester who specified the URL is displayed in the display area 2a of the requester terminal 2, and when the requester performs an operation to select the catalog viewing button G4a included in this screen G4, the control unit 30 executes the building materials catalog provision process (step S180) shown in FIG. 20, and displays the building materials data (e.g., FIG. 21) proposed by the proposer in the display area 2a of the requester terminal 2.

[0101] Currently, building material manufacturers and the like commercialize a huge variety of building materials (building materials and exterior construction materials) and create catalogs containing information about these materials (designs, prices, specifications, etc.) using paper materials or electronic data. Catalogs created using paper materials or electronic data (hereinafter referred to as "paper catalogs") are created individually by each building material manufacturer, and therefore their formats are not uniform and are inconsistent.

[0102] A proposer such as a house manufacturer receives consultations on construction, etc. from a client who is planning construction (new construction or renovation of a building, etc.) or exterior construction, etc., and selects the client's preferences and desired building materials, etc. that the proposer has learned from this consultation, from the above-mentioned paper catalog, etc., creates a document summarizing these selected building materials, etc., and proposes this created document to the client, thereby obtaining an order from the client for construction, etc. However, as mentioned above, paper catalogs have inconsistent formats and contain a huge variety of building materials, etc., so proposers have the problem of expending a great deal of effort on creating the documents to propose to the client.

[0103] On the other hand, when a client builds a house, for example, they tend to consult with multiple proposers rather than limiting themselves to one house builder or other proposer, and the client selects one from among these multiple proposers and requests the selected proposer to carry out the construction work, etc. and exterior construction work, etc. For this reason, it is difficult for proposers such as house builders to accept orders for the construction work, etc. and exterior construction work, etc. from all clients who come to them for consultation, and improving the acceptance rate is a challenge.

[0104] The system SY according to the first embodiment is a system that supports the work of a proposer, and the control unit 30 is configured to access the building materials database based on a request from the proposer to generate a building materials catalog (step S40 in FIG. 11), extract building materials data selected by the proposer from the building materials data stored in the building materials database, and generate building materials catalog data based on the extracted building materials data (step S50 in FIG. 11, FIG. 12). Therefore, the system SY can significantly reduce the proposer's effort required to create materials to propose to clients, and ultimately can improve the rate at which requests for construction, etc. are received from clients.

[0105] The system SY then stores the generated building materials catalog data in the building materials catalog DB (step S55 in FIG. 12), and the control unit 30 is configured to provide the building materials catalog data stored in the building materials catalog DB, in other words, the building materials data proposed by the proposer to the client, to the client (client terminal 2) based on a request from the client to view the building materials catalog, i.e., based on the client's operation specifying the URL sent to the client's email address (steps S180 and S190 in FIG. 19). This allows the client to view the building materials (building specifications) proposed by the proposer via the client terminal 2 without actually visiting the proposer. This allows the system SY to reduce the client's effort in consulting about construction, etc.

[0106] In particular, in the first embodiment, before the proposer and the client hold a meeting to discuss the specifications of the building and exterior, the proposer creates catalog data of building materials, etc. to be proposed to the client via the system SY, and the client can view this created catalog data of building materials, etc. via the system SY, so the client does not need to view the huge amount of paper catalogs provided by building material manufacturers, etc. This can significantly reduce the client's workload.

[0107] In system SY, when registering (storing) client data related to a new client in the client DB, the control unit 30 is configured to generate a URL corresponding to the new client based on a request from the proposer and send the generated URL to the client email address used by the corresponding client (step S90 in FIG. 15, step S94 in FIG. 16). The client can then browse the building materials catalog data (building materials data selected by the proposer) created for the client by specifying the URL sent to the client email address via the client terminal 2. In other words, the proposer can provide the client with a URL for browsing the building materials catalog data simply by registering the client data in the client DB. This not only reduces the proposer's workload but also prevents the generated URL from being mistakenly sent to a different client's email address.

[0108] In the first embodiment, data on building materials etc. relating to both building materials and exterior construction materials is stored in the building materials etc. DB, but the configuration may also include a separate database (hereinafter referred to as the "building materials DB") that stores only data relating to building materials (hereinafter referred to as "building materials data"), and a separate database (hereinafter referred to as the "exterior construction materials DB") that stores only exterior construction materials (hereinafter referred to as "exterior construction materials data").

[0109] In addition, in the first embodiment, there is provided a database (hereinafter referred to as the "building material catalog DB") that stores materials consisting only of building material data (hereinafter referred to as "building material catalog data"), and a database (hereinafter referred to as the "exterior construction material catalog DB") that stores materials consisting only of exterior construction material data (hereinafter referred to as "exterior construction material catalog data"), and the control unit 30 may be configured to generate building material catalog data based on the proposer's request and store this generated data in the building material catalog DB, while the control unit 30 may be configured to generate exterior construction material catalog data based on the proposer's request and store this generated data in the exterior construction material catalog DB.

[0110] In the first embodiment, the control unit 30 is capable of generating catalog data for building materials, etc., based on a request from the proposer, i.e., it is capable of generating both building material catalog data and exterior construction material catalog data, but it goes without saying that this configuration is not limited to this, and it may also be capable of generating either building material catalog data or exterior construction material catalog data, and providing this to the client based on the request from the client.

[0111] Next, a second embodiment of the present invention will be described with reference to the drawings.

[0112] FIG. 23 is an explanatory diagram for explaining an outline of the second embodiment.

[0113] The second embodiment differs from the first embodiment in that the proposer can create materials such as samples and templates of buildings and exterior structures (hereinafter referred to as "building sample catalogs"). In other words, in the second embodiment, not only can a building materials catalog (materials catalog) be created, but also materials (hereinafter referred to as "building sample catalogs") containing samples of building exteriors, interiors, and exterior structures (hereinafter referred to as "building samples") can be created.

[0114] In the following description, data relating to building samples will be referred to as "building sample data," and data relating to a building sample catalog will be referred to as "building sample catalog data."

[0115] The interior of a building includes the facilities and decoration of an entire room, the facilities and decoration of part of a room, and the facilities and decoration of areas other than the rooms, such as toilets, bathrooms, stairs, entrance halls, corridors, balconies, and storerooms.

[0116] In the second embodiment, the client can view not only the catalog of building materials, etc., but also the catalog of samples of buildings, etc. via the system SY. The following describes the differences from the first embodiment.

[0117] FIG. 24 is a block diagram showing the hardware configuration of the server 4 according to the second embodiment.

[0118] As shown in FIG. 24, the storage unit 20 includes a building sample database (hereinafter referred to as a "building sample DB") and a building sample catalog database (hereinafter referred to as a "building sample catalog DB").

[0119] The building sample DB stores sample data of buildings, etc.

[0120] FIG. 25 is a diagram illustrating an example of sample data of buildings, etc. stored in the building sample DB.

[0121] The building sample DB stores an ID (hereinafter referred to as a "building sample ID") that identifies the building sample data, linked to the name of the building sample (hereinafter referred to as a "building sample name"), images and videos showing the design of the building sample (hereinafter referred to as a "building sample image"), and other data (not shown; for example, data such as the actual size and material of the building sample). It goes without saying that, for example, instead of image b1, video b1 of building sample 1 may be linked to building sample ID 001.

[0122] The building sample catalog DB stores sample catalog data of buildings, etc.

[0123] FIG. 26 is a diagram for explaining an example of sample catalog data of buildings, etc. stored in the sample catalog DB of buildings, etc.

[0124] The building etc. sample catalog DB stores an ID (hereinafter referred to as the "building etc. sample catalog ID") that identifies the building etc. sample catalog data, linked to the name of the building etc. sample catalog (hereinafter referred to as the "building etc. sample catalog name"), and the building etc. sample ID associated with the building etc. sample listed in the building etc. sample catalog (which constitutes the building etc. sample catalog).

[0125] FIG. 27 is a diagram illustrating an example of requester data stored in the requester DB according to the second embodiment.

[0126] The requester DB stores a requester ID, linked to the requester name, the requester email address, a URL, a building materials catalog ID corresponding to the building materials catalog that the requester can view, and a building sample catalog ID corresponding to the building sample catalog that the requester can view.

[0127] FIG. 28 is a flowchart showing the processing executed between the proposer terminal 1 and the server 4.

[0128] 28 includes a process of storing the building etc. sample data in the building etc. sample DB. As shown in the figure, the control unit 30 executes a building etc. sample data storage process of storing the building etc. sample data transmitted from the proposer terminal 1 to the server 4 in the building etc. sample DB based on a request from the proposer to store the building etc. sample data in the building etc. sample DB (step S200).

[0129] Although the illustration of the building etc. sample data storage process (step S200) is omitted, when the control unit 30 receives building etc. sample data sent from the proposer terminal 1 to the server 4, it generates a building etc. sample ID corresponding to the received building etc. sample data, links the received building etc. sample data to the generated building etc. sample ID, and stores it in the building etc. sample DB.

[0130] For example, when the server 4 receives building sample data relating to building sample 1, as shown in Figure 25, it generates building sample id001 corresponding to building sample 1, and links this generated building sample id001 to building sample 1, which is the name of the building sample, building sample 1, image b1 of building sample 1, and other data (not shown), and stores them in the building sample DB.

[0131] FIG. 29 is a flowchart showing the processing executed between the proposer terminal 1 and the server 4.

[0132] 29 includes a process for generating a sample catalog of buildings, etc. As shown in the figure, the control unit 30 transmits the sample data of buildings, etc. stored in the sample DB of buildings, etc. to the proposer terminal 1 based on a view request from a proposer who wishes to view the sample data of buildings, etc. (Step S210). Upon receiving the sample data of buildings, etc. transmitted from the server 4, the proposer terminal 1 displays the received sample data of buildings, etc. in the display area 1a of the proposer terminal 1 (Step S220).

[0133] The proposer can select sample data of buildings, etc. that he / she wishes to propose to the client, according to the client's preferences, etc., from the sample data of buildings, etc. displayed in the display area 1a of the proposer terminal 1 in step S220.

[0134] The proposer terminal 1 transmits the sample data of buildings, etc. selected by the proposer to the server 4 based on the operation of the proposer (step S230). The control unit 30 executes a process of generating sample catalog data of buildings, etc. (sample catalog data generation process of buildings, etc.) based on receiving the sample data of buildings, etc. transmitted from the proposer terminal 1 (step S240).

[0135] FIG. 30 is a flowchart showing the process of generating sample catalog data of buildings etc. (step S240).

[0136] As shown in FIG. 30, first, the control unit 30 refers to the building etc. sample DB to identify the building etc. sample data received in step S240 (step S241). Next, the control unit 30 identifies the building etc. sample ID associated with the building etc. sample data identified in step S241 (step S242). Next, the control unit 30 generates a building etc. sample catalog ID (step S243). Next, the control unit 30 generates a building etc. sample catalog name (step S244). Finally, the control unit 30 associates the building etc. sample catalog ID identified in step S242 and the building etc. sample catalog name generated in step S244 with the building etc. sample catalog ID generated in step S243, stores them in the building etc. sample catalog DB (step S245), and terminates the building etc. sample catalog data generation process.

[0137] For example, suppose that building etc. sample 1 and building etc. sample 3 are received in step S240. That is, suppose that the proposer selects building etc. sample 1 and building etc. sample 3 as the building etc. samples that he or she wishes to propose to the requester. In this case, the control unit 30 refers to the building etc. sample DB (see FIG. 25) in step S242 to identify building etc. sample id001 corresponding to building etc. sample 1 and building etc. sample id003 corresponding to building etc. sample 3, generates building etc. sample catalog id001 in step S243 (see FIG. 26), generates building etc. sample catalog 1 (building etc. sample catalog name) in step S244 (see FIG. 26), and links building etc. sample id001, building etc. sample id003, and building etc. sample catalog 1 to building etc. sample catalog id001 in step S255, and stores them in the building etc. sample catalog DB (see FIG. 26).

[0138] In the first embodiment, in step S244 of the building etc. sample catalog generation process, the control unit 30 generates a building etc. sample catalog name and stores this generated building etc. sample catalog name in the building etc. sample catalog DB, but the present invention is not limited to this configuration, and the proposer may formulate a building etc. sample catalog name and transmit this formulated building etc. sample catalog name to the server 4, thereby storing the building etc. sample catalog name in the building etc. sample catalog DB. In short, the proposer may assign a building etc. sample catalog name.

[0139] FIG. 31 is a flowchart showing the processing executed between the proposer terminal 1 and the server 4.

[0140] 31 includes a process of linking the requester data stored in the requester DB with the building sample catalog stored in the building sample catalog DB (in other words, a process of providing the requester with a building material sample catalog created by the proposer for the requester). As shown in the figure, the control unit 30 accesses the requester DB based on a request from the proposer to view the requester data stored in the requester DB, and transmits the requester data stored in the requester DB to the proposer terminal 1 (step S250). Upon receiving the requester data transmitted from the control unit 30, the proposer terminal 1 displays the received requester data in the display area 1a of the proposer terminal 1 (step S260).

[0141] The proposer can use the input device of the proposer terminal 1 to select the requester data for which he / she wishes to provide sample catalog data of buildings, etc. from the requester data displayed in the display area 1a of the proposer terminal 1 in step S260.

[0142] The proposer terminal 1 transmits the requester name data selected by the proposer to the server 4 based on the operation of the proposer (step S270). Based on receiving the requester name data transmitted from the proposer terminal 1, the control unit 30 temporarily stores the received requester name data in the storage unit 20, and also accesses the building etc. sample catalog DB and transmits the building etc. sample catalog data stored in the building etc. sample catalog DB to the proposer terminal 1 (step S280). Based on receiving the building etc. sample catalog data transmitted from the control unit 30, the proposer terminal 1 displays the received building etc. sample catalog data in the display area 1a of the proposer terminal 1 (step S290).

[0143] The proposer can use the input device of the proposer terminal 1 to select the sample building catalog data of the building, etc. that he / she wishes to provide to the requester from the sample building catalog data of the building, etc. displayed in the display area 1a of the proposer terminal 1 in step S290.

[0144] The proposer terminal 1 transmits the sample catalog data of buildings, etc. selected by the proposer to the server 4 based on the operation of the proposer (step S300). Based on receiving the sample catalog data of buildings, etc. transmitted from the proposer terminal 1, the control unit 30 executes a process of linking the requester data with the sample catalog data of buildings, etc. (sample catalog data linking process of buildings, etc.) (step S310).

[0145] FIG. 32 is a flowchart showing the building sample catalog linking process (step S310).

[0146] First, the control unit 30 refers to the requester DB to identify the requester ID associated with the requester name data temporarily stored in step S280 (step S311). Next, the control unit 30 refers to the building etc. sample catalog DB to identify the building etc. sample catalog ID associated with the building etc. sample catalog data received in step S310 (step S312). Finally, the control unit 30 links the requester ID identified in step S311 with the building etc. sample catalog ID identified in step S312 (step S313), and ends the building etc. sample catalog linking process.

[0147] For example, suppose that requester ID001 is identified in step S311, and building etc. sample catalogue ID001 is identified in step S312. In other words, suppose that a proposer proposes building etc. sample catalogue 1 to requester Y1. In this case, the control unit 30 associates the identified requester ID001 with building etc. sample catalogue ID001 (see FIG. 27).

[0148] In the first embodiment, as shown in Figure 27, the client ID stored in the client DB is linked to the building etc. sample catalog ID, but this configuration is not limited to this as long as the client ID and the building etc. sample catalog ID are linked.For example, the configuration may be such that the client ID 001 is linked to the building etc. sample catalog ID 001 stored in the building etc. sample catalog DB, or a separate database may be set up and information linking the client ID 001 and the building etc. sample catalog ID 001 may be stored in that database.

[0149] FIG. 33 is a flowchart showing the processing executed between the client terminal 2 and the server 4.

[0150] The process shown in Fig. 33 includes a process in which a requester browses sample data of buildings, etc. (sample catalog data of buildings, etc.). The requester terminal 2 requests the server 4 to browse the sample catalog of buildings, etc. (step S320) based on the requester's operation specifying the URL sent to the email address used by the requester (see step S94 of Fig. 16; the issued URL). The control unit 30, based on receiving the request to browse the sample catalog of buildings, etc. from the requester, executes a process to provide the sample catalog data of buildings, etc. to the requester (a process to provide the sample catalog of buildings, etc.) (step S330).

[0151] FIG. 34 is a flowchart showing the process of providing a sample catalog of buildings, etc. (step S330).

[0152] First, the control unit 30 refers to the client DB to identify the building etc. sample catalog ID corresponding to the URL specified in step S320 (step S331). Next, the control unit 30 refers to the building etc. sample catalog DB to identify the building etc. sample ID associated with the building etc. sample catalog ID specified in step S331 (step S332). Next, the control unit 30 refers to the building etc. sample DB to identify the building etc. sample data corresponding to the building etc. sample ID specified in step S332 (step S333). Next, the control unit 30 extracts the building etc. sample data specified in step S333 from the building etc. sample DB (step S334). Finally, the control unit 30 transmits the building etc. sample data extracted in step S334 to the client terminal 2 that specified the URL (step S335), and ends the building sample catalog provision process.

[0153] For example, suppose that in step S320, the requester Y1 specifies the URL issued to the requester Y1 using the requester terminal 2. In this case, in step S331, the control unit 30 refers to the requester DB to identify the building etc. sample catalog id001 associated with the requester id001 of the requester Y1 (see FIG. 27), then in step S332, refers to the building etc. sample catalog DB to identify the building etc. sample id001 and id003 associated with the building etc. sample catalog id001 (see FIG. 26), then in step S333, refers to the building etc. sample DB to identify the building etc. sample data corresponding to the building etc. sample id001 and id003 (see FIG. 25), then in step S334, extracts the building etc. sample data related to the building etc. samples 1 and 3, and finally in step S335, transmits the building etc. sample data related to the building etc. samples 1 and 3 to the requester terminal 2 used by the requester Y1.

[0154] Returning to the explanation of Figure 33, upon receiving the sample data of buildings, etc. sent from the server 4, the client terminal 2 displays the received sample data of buildings, etc. in the display area 2a of the client terminal 2 (step S340).

[0155] FIG. 35 is a diagram schematically showing an example of the screen G5.

[0156] FIG. 35 is a screen showing an example of sample data of buildings, etc., displayed in the display area 2a of the client terminal 2 in step S340.

[0157] 35, screen G5 includes an area G5a that displays building etc. sample data related to building etc. sample 1, and an area G5b that displays building etc. sample data related to building etc. sample 3. Area G5a includes arrows G5a1 and G5a2. Area G5b includes arrows G5b1 and G5b2. Arrows G5a1, G5a2, G5b1, and G5b2 are used to change the building etc. sample data displayed in the corresponding areas G5a and G5a.

[0158] The requester terminal 2 changes the building etc. sample data related to the building etc. sample 1 displayed in the area G5a each time the requester performs an operation to select, for example, arrows G5a1 and G5a2 included in the area G5a. For example, when an image b1 of the building etc. sample 1 is displayed in the area G5a and the requester performs an operation to select the arrow G5a1 once, an image of the building etc. sample 1 different from the image b1 is displayed in the area G5a, and when an image of the building etc. sample 1 different from the image b1 is displayed in the area G5a and the requester performs an operation to select the arrow G5a2 once, the image b1 of the building etc. sample 1 is displayed in the area G5a.

[0159] In the second embodiment, the sample data of buildings, etc. proposed by the proposer (e.g., Figure 35) is displayed in the display area 2a of the requester terminal 2 based on the requester's operation of specifying a URL (step S340). However, this configuration is not limited to this. For example, based on the requester's operation of specifying a URL, first, a screen G4 (Figure 36) dedicated to the requester who specified the URL is displayed in the display area 2a of the requester terminal 2, and when the requester performs an operation on screen G4 of Figure 36 to select the building, etc. sample catalog viewing button G4b included in screen G4, the control unit 30 executes the building, etc. sample catalog provision process shown in Figure 33, and displays the sample data of buildings, etc. proposed by the proposer (e.g., screen G5 of Figure 35) in the display area 2a of the requester terminal 2.

[0160] As described above, in the system SY according to the second embodiment, the control unit 30 is configured to access the building sample DB based on a request from a proposer to generate a building sample catalog (step S230), extract the building sample data selected by the proposer from the building sample data stored in the building sample DB, and generate building sample catalog data based on the extracted building sample data (step S240). Therefore, the system SY can significantly reduce the proposer's effort required to prepare materials to propose to clients, and ultimately improve the success rate of receiving requests for building and exterior construction work from clients.

[0161] The system SY then stores the generated building sample data in a building sample catalog DB (step S245 in FIG. 30), and the control unit 30 is configured to provide the client (client terminal 2) with the building sample catalog data stored in the building sample catalog DB, in other words, the building sample data proposed by the proposer to the client, based on a request from the client to view the building sample catalog (step S330 in FIG. 33). This allows the client to view the building sample proposed by the proposer via the client terminal 2 without actually visiting the proposer. This allows the system SY to reduce the client's effort in consulting about architecture, etc.

[0162] In particular, in the second embodiment, before the proposer and the client hold a meeting to discuss the specifications of the building or exterior, the proposer creates catalog data of building materials, etc. and sample catalog data of the building, etc. to be proposed to the client via the system SY, and the client can view both the catalog data of building materials, etc. and the sample catalog data of the building, etc. created by the proposer via the system SY. This allows the client to consider the specifications of the building or exterior that meet their desires in advance without having to view the above-mentioned paper catalog, and can then hold a meeting with the proposer after such consideration.

[0163] In the second embodiment, data relating to both building and exterior samples is stored in the building sample DB, but the configuration may also include a separate database (hereinafter referred to as the "building sample DB") that stores only data relating to building samples (hereinafter referred to as "building sample data"), and a separate database (hereinafter referred to as the "exterior sample DB") that stores only data relating to exterior samples (hereinafter referred to as "exterior sample data").

[0164] In the second embodiment, the system SY is provided with a database (hereinafter referred to as the "building sample catalog DB") that stores materials consisting only of building sample data (hereinafter referred to as "building sample catalog data"), and a database (hereinafter referred to as the "exterior sample catalog DB") that stores materials consisting only of exterior sample data (hereinafter referred to as "exterior sample catalog data"). The control unit 30 may be configured to generate building sample catalog data based on the request of the proposer and store this generated data in the building sample catalog DB, while the control unit 30 may be configured to generate exterior sample catalog data based on the request of the proposer and store this generated data in the exterior sample catalog DB.

[0165] In the second embodiment, the control unit 30 is configured to be able to generate both building sample catalog data and exterior sample catalog data based on a request from the proposer, but it goes without saying that this configuration is not limited to this, and the control unit 30 may be configured to be able to generate only one of the building sample catalog data and the exterior sample catalog data.

[0166] In addition, in the second embodiment, the configuration may be such that a database (hereinafter referred to as a "building exterior sample DB") that stores only data related to building exterior samples (hereinafter referred to as "building exterior sample data") and a database (hereinafter referred to as a "building exterior sample DB") that stores only data related to building interior samples (hereinafter referred to as "building interior sample data") are separately provided, or a database (hereinafter referred to as a "building exterior sample catalog DB") that stores materials composed only of building exterior sample data (hereinafter referred to as "building exterior sample catalog data") and a database (hereinafter referred to as a "building interior sample catalog DB") that stores materials composed only of building interior sample data (hereinafter referred to as "building interior sample catalog data") may be provided, and the control unit 30 generates building exterior sample catalog data based on a request from the proposer and stores this generated data in the building exterior sample catalog DB, while the control unit 30 generates building interior sample catalog data based on a request from the proposer and stores this generated data in the building interior sample catalog DB.

[0167] In the second embodiment, the control unit 30 is configured to be able to generate sample catalog data for buildings, etc. based on a request from a proposer, that is, to be able to generate all of the building sample catalog data, exterior sample catalog data, building exterior sample catalog data, and building interior sample catalog data. However, it goes without saying that the configuration is not limited to this, and the control unit 30 may be configured to be able to generate any one or more sample catalog data from the building sample catalog data, exterior sample catalog data, building exterior sample catalog data, and building interior sample catalog data, and provide this to the client based on the request from the client.

[0168] The systems and programs in the first and second embodiments can be modified in various ways without departing from the spirit of the present invention. The order of control can also be modified as needed as long as the desired effect is achieved.

[0169] (Configuration 1) A system SY that supports a proposer who proposes building and exterior specifications to a client is provided with a control unit 30, which, based on a request from the proposer, accesses a database that stores material data (building material data, etc.) related to building and exterior materials, extracts material data selected by the proposer from the material data stored in this database, generates catalog data (building material catalog data, etc.) including the extracted material data, and, based on a request from the client, provides the catalog data generated by the control unit 30 to the client.

[0170] (Configuration 2) A system SY that supports a proposer who proposes building specifications to a client is provided with a control unit 30, which, based on a request from the proposer, accesses a database that stores material data (building material data) related to building materials, extracts material data selected by the proposer from the material data stored in this database, generates catalog data (building material catalog data) including the extracted material data, and, based on a request from the client, provides the catalog data generated by the control unit 30 to the client.

[0171] (Configuration 3) A system SY that supports a proposer who proposes specifications for an exterior structure to a client is provided with a control unit 30, which, based on a request from the proposer, accesses a database that stores material data (exterior structure material data) related to the exterior structure, extracts material data selected by the proposer from the material data stored in this database, generates catalog data (exterior structure material catalog data) including the extracted material data, and, based on a request from the client, provides the catalog data generated by the control unit 30 to the client.

[0172] (Configuration 4) The control unit 30 is a system characterized by accessing a database that stores sample data (building, etc. sample data) related to building samples and exterior structure samples based on a request from the proposer, extracting sample data selected by the proposer from the sample data stored in this database, generating sample catalog data (building, etc. sample catalog data) including the extracted sample data, and providing the sample catalog data generated by the control unit 30 to the client based on a request from the client.

[0173] (Configuration 5) The control unit 30 is a system characterized by accessing a database that stores sample data (building sample data) related to building samples based on a request from the proposer, extracting sample data selected by the proposer from the sample data stored in this database, generating sample catalog data (building sample catalog data) including the extracted sample data, and providing the sample catalog data generated by the control unit 30 to the client based on a request from the client.

[0174] (Configuration 6) The control unit 30 is a system characterized by accessing a database that stores sample data (exterior sample data) related to exterior samples based on a request from a proposer, extracting sample data selected by the proposer from the sample data stored in this database, generating sample catalog data (exterior sample catalog data) including the extracted sample data, and providing the sample catalog data generated by the control unit 30 to the client based on a request from the client.

[0175] (Configuration 7) The control unit 30 is a system characterized by accessing a database that stores sample data (building exterior sample data) related to building exterior samples based on a request from a proposer, extracting sample data selected by the proposer from the sample data stored in this database, generating sample catalog data (building exterior sample catalog data) including the extracted sample data, and providing the sample catalog data generated by the control unit 30 to the client based on a request from the client.

[0176] (Configuration 8) The control unit 30 is a system characterized by accessing a database that stores sample data relating to building interior samples (building interior sample data) based on a request from a proposer, extracting sample data selected by the proposer from the sample data stored in this database, generating sample catalog data (building interior sample catalog data) including the extracted sample data, and providing the sample catalog data generated by the control unit 30 to the client based on a request from the client.

[0177] (Configuration 9) The control unit 30, upon receiving a request from a proposer, stores (registers) client data relating to a client (new client) in a database, generates a URL corresponding to the client, sends the generated URL to the email address used by the client corresponding to the URL, and, based on the client's operation of specifying the URL, accesses the database, extracts catalog data corresponding to the specified URL (building materials catalog data, building materials catalog data, exterior construction materials catalog data, building sample catalog data, building sample catalog data, exterior construction sample catalog data, building exterior sample data, building interior sample data, some of these catalog data, or all of these catalog data), and provides the extracted catalog data to the client. [Explanation of symbols]

[0178] SY System 1. Proposer terminal 2. Client terminal 4 Server (support device) 20 Memory section 30 Control Unit

Claims

1. A support system for supporting a proposer who proposes specifications of at least one of a building and an exterior structure to a client, A control unit is provided, The control unit accessing a database storing material data related to building materials and / or exterior materials based on a request from the proposer, extracting material data selected by the proposer from the stored material data, and generating catalog data including the extracted material data; The catalog data generated by the control unit is provided to the requester based on a request from the requester. A support system characterized by:

2. The control unit accessing a database that stores sample data relating to building samples and / or exterior structure samples based on a request from the proposer, extracting sample data selected by the proposer from the stored sample data, and generating sample catalog data including the extracted sample data; The sample catalog data generated by the control unit is provided to the client based on a request from the client.

2. The support system according to claim 1.

3. The control unit When storing client data relating to the client in a database based on a request from the proposer, generating a URL corresponding to the client and sending the generated URL to an email address used by the client corresponding to the URL; The catalog data generated by the control unit and the sample catalog data are provided to the client based on the URL specified by the client.

3. The support system according to claim 2.

4. A support device that supports a proposer who proposes specifications of at least one of a building and an exterior structure to a client, A control unit is provided, The control unit accessing a database storing material data related to building materials and / or exterior materials based on a request from the proposer, extracting material data selected by the proposer from the stored material data, and generating material catalog data including the extracted material data; Based on a request from the client, the material catalog data generated by the control unit is provided to the client.

1. A support device comprising:

5. The control unit accessing a database that stores sample data relating to building samples and / or exterior structure samples based on a request from the proposer, extracting sample data selected by the proposer from the stored sample data, and generating sample catalog data including the extracted sample data; The sample catalog data generated by the control unit is provided to the client based on a request from the client.

5. The support device according to claim 4.

6. The control unit When storing client data relating to the client in a database based on a request from the proposer, generating a URL corresponding to the client and sending the generated URL to an email address used by the client corresponding to the URL; The catalog data generated by the control unit and the sample catalog data are provided to the client based on the URL specified by the client.

6. The support device according to claim 5.

Images