Support systems, support devices, support methods
The support system addresses the inefficiency in proposing building specifications by allowing proposers to reduce and select data displayed on their terminal, ensuring the proposed specifications meet the requester's wishes.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- ARCHI VILLAGE INC
- Filing Date
- 2024-10-18
- Publication Date
- 2026-05-01
AI Technical Summary
Existing systems fail to efficiently propose building specifications that meet the wishes of the requester.
A support system that assists proposers by displaying specification data on a terminal, reducing the number of displayed data through proposer operations, and selectively showing only the requested data to the client based on the proposer's input.
The system efficiently proposes building specifications aligned with the requester's preferences, enhancing the accuracy and relevance of the proposed data.
Smart Images

Figure 2026072125000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a technology for assisting a proposer who proposes building specifications to a requester.
Background Art
[0002] Patent Document 1 discloses a technology related to a system for reducing the burden on contractors in preparing estimates. Patent Document 2 discloses a technology related to a system that can easily search for design information related to buildings. Patent Document 3 discloses a technology related to a system for proceeding with various construction operations with the approval of three parties: the client, the supervisor, and the contractor.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Patent Document 2
Patent Document 3
Summary of the Invention
Problems to be Solved by the Invention
[0004] Conventionally, there has been a demand for a system that can efficiently propose building specifications that meet the wishes of the requester to the requester.
[0005] The present invention has been made in view of the above points, and its object is to provide a system that can efficiently propose building specifications that meet the wishes of the requester to the requester.
Means for Solving the Problems
[0006] As a means for achieving the above object, the support system of the present invention is A support system that assists proposers who propose building specifications to clients, It comprises a control unit and a memory unit, The aforementioned storage unit stores specification data related to the specifications of the building. The control unit, A first display means that displays the specification data stored in the storage unit in the first display area of the terminal used by the proposer, A reduction means for reducing the number of specification data displayed in the first display area by the proposer's operation, The system includes a second display means that displays only the specification data selected by the proposer's operation from the specification data displayed in the first display area of the first display means in the second display area of the terminal used by the client. It is characterized by the following:
[0007] As a means of achieving the above objective, The support device of the present invention is A support device for a proposer who proposes building specifications to a client, It comprises a control unit and a memory unit, The aforementioned storage unit stores specification data related to the specifications of the building. The control unit, A first display means that displays the specification data stored in the storage unit in the first display area of the terminal used by the proposer, A reduction means for reducing the number of specification data displayed in the first display area by the proposer's operation, The system includes a second display means that displays only the specification data selected by the proposer's operation from the specification data displayed in the first display area of the first display means in the second display area of the terminal used by the client. It is characterized by the following:
[0008] As a means of achieving the above objective, The support method of the present invention is A support method for assisting proposers who propose building specifications to clients, Based on the request of the proposer, displaying specification data regarding the specifications of the building stored in the storage unit in the first display area of the terminal used by the proposer; Based on the request of the proposer, reducing the number of specification data to be displayed in the first display area; Based on the request of the proposer, selecting the specification data to be proposed to the requester from the specification data displayed in the first display area; Based on the request of the requester, displaying only the specification data selected based on the request of the proposer in the second display area of the terminal used by the requester, and including is characterized by.
Effect of the Invention
[0009] The present invention can efficiently propose the specifications of a building in line with the wishes of the requester to the requester.
Brief Description of the Drawings
[0010] [Figure 1] It is an explanatory diagram for explaining the outline according to the present embodiment of the present invention. [Figure 2] It is a schematic diagram showing the system configuration according to the present embodiment. [Figure 3] It is a block diagram showing the hardware configuration of the first server according to the present embodiment. [Figure 4] It is a diagram schematically showing the building material data stored in the building material DB according to the present embodiment. [Figure 5] It is a block diagram showing the hardware configuration of the second server according to the present embodiment. [Figure 6] It is a diagram schematically showing the project data stored in the project DB according to the present embodiment. [Figure 7] It is a flowchart showing a part of the processing in the system according to the present embodiment. [Figure 8] It is a flowchart showing a part of the processing in the system according to the present embodiment. [Figure 9]It is a flowchart showing the case registration process according to this embodiment. [Figure 10] It is a flowchart showing a part of the processing in the system according to this embodiment. [Figure 11] It is a diagram schematically showing an example of a screen according to this embodiment. [Figure 12] It is a flowchart showing a part of the processing in the system according to this embodiment. [Figure 13] It is a diagram schematically showing an example of a screen according to this embodiment. [Figure 14] It is a flowchart showing a part of the processing in the system according to this embodiment. [Figure 15] It is a diagram schematically showing an example of a screen according to this embodiment. [Figure 16] It is a diagram schematically showing an example of a screen according to this embodiment. [Figure 17] It is a flowchart showing a part of the processing in the system according to this embodiment. [Figure 18] It is a diagram schematically showing the case data stored in the case DB according to this embodiment. [Figure 19] It is a diagram schematically showing an example of a screen according to this embodiment. [Figure 20] It is a diagram schematically showing an example of a label according to this embodiment. [Figure 21] It is a flowchart showing a part of the processing in the system according to this embodiment. [Figure 22] It is a diagram schematically showing an example of a screen according to this embodiment. [Figure 23] It is a diagram schematically showing the case data stored in the case DB according to this embodiment. [Figure 24] It is a flowchart showing a part of the processing in the system according to this embodiment. [Figure 25] It is a diagram schematically showing an example of a screen according to this embodiment. [Figure 26] It is a diagram schematically showing an example of a label according to this embodiment. [Figure 27] This is a flowchart showing a portion of the processing within the system according to this embodiment. [Figure 28] This figure schematically shows an example of a screen according to this embodiment. [Figure 29] This diagram schematically shows the case data stored in the case database according to this embodiment. [Figure 30] This is a flowchart showing a portion of the processing within the system according to this embodiment. [Figure 31] This figure schematically shows an example of a screen according to this embodiment. [Figure 32] This figure schematically shows an example of a sign according to this embodiment. [Figure 33] This is a flowchart showing a portion of the processing within the system according to this embodiment. [Figure 34] This figure schematically shows an example of a screen according to this embodiment. [Figure 35] This diagram schematically shows the case data stored in the case database according to this embodiment. [Figure 36] This is a flowchart showing a portion of the processing within the system according to this embodiment. [Figure 37] This figure schematically shows an example of a screen according to this embodiment. [Figure 38] This is a flowchart showing a portion of the processing within the system according to this embodiment. [Figure 39] This figure schematically shows an example of a screen according to a modified version of this embodiment. [Figure 40] This figure schematically shows an example of a screen according to a modified version of this embodiment. [Modes for carrying out the invention]
[0011] Hereinafter, embodiments of the present invention (this embodiment) will be described with reference to the drawings.
[0012] Figure 1 is an explanatory diagram illustrating the outline of this embodiment.
[0013] The clients shown in Figure 1 are those (including both individuals and corporations) who desire, consider, or plan the construction, renovation, remodeling, and repair of buildings, as well as the construction, installation, and maintenance of exterior structures (so-called landscaping).
[0014] In the following explanation, the term "building" refers collectively to both the building itself and its surrounding structures.
[0015] As shown in Figure 1, the proposers are those who propose building specifications to the client. Proposers include, for example, house builders, construction companies, developers, housing sales agencies, housing sales brokers, architectural design firms, construction management firms, and individual contractors engaged in construction.
[0016] The proposer will suggest to the client the specifications of the building, including the building materials, the building's exterior (examples of completed buildings), and the building's interior (e.g., the design of rooms, corridors, stairs, etc.).
[0017] In the following explanation, building materials are referred to as "building materials."
[0018] Building materials broadly include, for example, gates, coping (horizontal beams placed on top of gates, etc.), entrance arches, doors, fences, railings, lighting, mailboxes, parcel boxes, nameplates, locks, intercoms, walls, coping stones (stones placed on top of walls, etc.), handrails, fences, garages, garden facilities (plants, trees, artificial ponds, etc.), balconies, windows, wallpaper, building accessories, and exterior accessories.
[0019] As shown in Figure 1, the proposer, via the SY system, proposes building specifications to the client that are tailored to the client's preferences and current needs.
[0020] This embodiment describes a case where the proposer proposes building materials to the client. In other words, only the case where the proposer proposes building materials as part of the building specifications will be described. The case where the proposer proposes the exterior and interior of the building to the client is the same as the case where building materials are proposed, so these explanations will be omitted.
[0021] System SY is equipped with a building materials database (hereinafter referred to as "building materials DB") for storing (accumulating) data related to building materials (hereinafter referred to as "building materials data"). The proposer selects the building materials data to propose to the client from the building materials data stored in the building materials DB, and System SY is configured to provide the client only with the building materials data selected by the proposer from the building materials data stored in the building materials DB (details below).
[0022] The data storers shown in Figure 1 are those who store building material data in the building material database. These data storers include, for example, manufacturers that produce, sell, or develop building materials, those who manage the system SY, and assistants who support these managers.
[0023] In this embodiment, storing building material data in the building material database requires an ID or similar identifier to identify the person storing the data. Those who do not possess such an ID cannot store building material data in the building material database. In other words, access to building material data storage in the building material database is restricted.
[0024] In this embodiment, the proposer is configured to select building material data to propose to the client from the building material data stored in the building material database. Therefore, the storage entity is expected to store building material data that the proposer can propose to the client (for example, data related to existing building materials commercialized by manufacturers) in the building material database, while not storing building material data related to non-general-purpose building materials that are individually manufactured according to the client's requests, or building material data related to hobby or personal materials that have not been commercialized.
[0025] Figure 2 is a schematic diagram showing the configuration of system SY according to this embodiment.
[0026] System SY includes proposer terminal 1, requester terminal 2, storage terminal 3, first server 4, and second server 5.
[0027] Proposer terminal 1 is a terminal (communication terminal, e.g., a personal computer) used by the proposer. Proposer terminal 1 has input devices (e.g., a keyboard and mouse) and output devices (e.g., a display). The output device of proposer terminal 1 has a first display area 1a that displays a predetermined screen (image).
[0028] Client terminal 2 is a terminal (communication terminal, such as a personal computer) used by the client. Client terminal 2 has an input device and an output device. The output device of client terminal 2 has a second display area 2a that displays a predetermined screen.
[0029] The storage terminal 3 is a terminal (communication terminal, such as a personal computer) used by the storage user. The storage terminal 3 has an input device and an output device.
[0030] The first server 4 is an information processing device. The first server 4 has programs installed for performing various processing tasks. The first server 4 is, for example, built on the cloud.
[0031] In this embodiment, the first server 4 is equipped with the aforementioned building materials database. The building materials data stored in the building materials database is configured to be viewable via a first web page (not shown), and a first URL is used to specify the first web page. The proposer terminal 1 displays the building materials data stored in the building materials database in the first display area 1a by specifying the first URL. Note that URL is an abbreviation for "uniform resource locator".
[0032] In the following explanation, the building material data stored in the building material database will be referred to as "first building material data".
[0033] The second server 5 is an information processing device. The second server 5 has programs installed for performing various processing tasks. The second server 5 connects to the proposer terminal 1 via network N. The second server 5 is, for example, built on the cloud.
[0034] In this embodiment, the first building material data is configured to be viewable by specifying the first URL, but it can also be viewed by connecting the proposer's terminal 1 to the second server 5 and accessing it via the second server 5 (details will be described later).
[0035] In this embodiment, the building material data proposed by the proposer to the client is made accessible via a second web page (not shown), and a second URL is used to specify the second web page. The second URL is configured to be generated for each client. By specifying the second URL, the client can view the building material data proposed by the proposer for each client (details will be described later).
[0036] As a variation of this embodiment, the client terminal 2 may be configured to connect to the second server 5 via an ID (account) that identifies the client, thereby displaying the building material data proposed by the proposer for each client in the second display area 2a.
[0037] Figure 3 is a block diagram showing the hardware configuration of the first server 4.
[0038] The first server 4 includes a first storage unit 20 and a first control unit 30. The first storage unit 20 and the first control unit 30 are electrically connected via a communication bus (not shown).
[0039] The first storage unit 20 includes ROM, RAM, and a hard disk (not shown). The first storage unit 20 stores programs executed by the first control unit 30. The first storage unit 20 also includes a building materials database for storing building materials data.
[0040] Figure 4 is a diagram illustrating an example of building material data stored in the building materials database.
[0041] Building material data includes image and video data related to the design (shape, pattern, and color composition) of building materials (hereinafter referred to as "building material image data"), data related to the category to which the building material belongs (hereinafter referred to as "building material category data"), data of manufacturers supplying building materials to the market (hereinafter referred to as "building material manufacturer data"), data of product names and serial numbers of building materials (hereinafter referred to as "building material name data"), data on various dimensions of building materials such as height and width, as well as color, weight, material, durability, etc. (hereinafter referred to as "building material specification data"), data on the price of building materials (hereinafter referred to as "building material price data"), and other data.
[0042] The building materials database stores building material image data, building material category data, building material manufacturer data, building material name data, building material specification data, building material price data, and other data, each associated with an identifier (hereinafter referred to as "building material ID") that identifies building material data.
[0043] In one example shown in Figure 4, the building material database stores building material data associated with building material id001, building material data associated with building material id002, building material data associated with building material id003, building material data associated with building material id004, building material data associated with building material id005, building material data associated with building material id006, and other building material data (not shown).
[0044] As shown in Figure 4, for example, building material id001 is associated with gate a1 (building material name data), image a1 of gate a1 (building material image data), gate (building material category data), manufacturer A (building material manufacturer data), height 100cm (building material specification data), and 200,000 yen (building material price data).
[0045] Needless to say, as a variation of this embodiment, a video of gate a1 a1 may be linked to building material id001 instead of image a1.
[0046] Let's return to the explanation in Figure 3. The first control unit 30 is configured to extract all or part of the first building material data based on access from the second server 5 and send the extracted building material data to the second server 5. The building material data received by the second server 5 is displayed in the first display area 1a (details will be described later).
[0047] Figure 5 is a block diagram showing the hardware configuration of the second server 5.
[0048] The second server 5 includes a second storage unit 40 and a second control unit 50. The second storage unit 40 and the second control unit 50 are electrically connected via a communication bus (not shown).
[0049] The second storage unit 40 includes ROM, RAM, and a hard disk (not shown). The second storage unit 40 stores programs executed by the second control unit 50. The second storage unit 40 also includes a case database (hereinafter referred to as "case DB").
[0050] The case database stores case data (hereinafter referred to as "case data") that identifies requests from clients.
[0051] Figure 6 is a diagram illustrating an example of case data stored in the case database.
[0052] The project data includes data related to the project name (hereinafter referred to as "project name data"), data related to the name of the project client (hereinafter referred to as "client data"), the email address used by the client (hereinafter referred to as "client email address"), the aforementioned second URL, and other data.
[0053] The case database stores case data, along with the case name, client data, client email address, second URL, and other data, each associated with a unique case ID (hereinafter referred to as "case ID").
[0054] In the example shown in Figure 6, the project database stores project data associated with, for example, project ID 001 and project data associated with project ID 002. As shown in the figure, for example, project ID 001 is associated with "New Construction of Y1" (project name data), "Y1" (client data), "xxx@xxx" (client email address), and "httpxx" (second URL).
[0055] The second URL is for the client to view the building material data proposed by the proposer, and is configured to be generated for each project that identifies the client's request (details below).
[0056] In the following explanation, the case (case data) corresponding to case id001 requested by Y1 will be referred to as the "Y1 case" as appropriate.
[0057] Returning to the explanation of Figure 5, the second control unit 50 includes a CPU, ROM, and RAM (not shown). The second control unit 50 performs various processes by reading the program stored in the second storage unit 40 and loading it onto the RAM. The second control unit 50 includes a first display means 51, a reduction means 52, a second display means 53, and other means (not shown).
[0058] The first display means 51 controls the display of building material data (first building material data) stored in the building material DB (storage unit) in the first display area 1a. The reduction means 52 controls the reduction of the number of building material data displayed by the first display means 51 in the first display area 1a according to the proposer's operation. The second display means 53 controls the display of only the building material data selected by the proposer from the building material data displayed by the first display means 51 in the first display area 1a in the second display area 2a.
[0059] Next, the processing by the first control unit 30, the processing by the second control unit 50, and the processing by the second control unit 50 and the first control unit 30 will be explained. In the following explanation, it is assumed that the proposer terminal 1 is connected to the second server 5 via an ID (account) that identifies the proposer, and that the storage terminal 3 is connected to the first server 4 via an ID that identifies the storage.
[0060] Figure 7 is a flowchart showing the process executed between the storage terminal 3 and the first server 4.
[0061] The process shown in Figure 7 includes the process of storing new building material data that is not yet stored in the building material database in the building material database. As shown in the figure, the storage terminal 3 transmits the new building material data to the first server 4 based on a request to store the new building material data in the building material database (step S1). When the first server 4 receives the building material data transmitted from the storage terminal 3, the first control unit 30 executes the process of storing the received building material data in the building material database (building material data storage process) (step S10).
[0062] Regarding step S10, although not shown in the diagram, when the first control unit 30 receives building material data transmitted from the storage terminal 3 to the first server 4, it generates a building material ID corresponding to the received building material data, associates the received building material data with this generated building material ID, and stores them in the building material DB.
[0063] For example, suppose in step S1, the storage terminal 3 sends building material data (see Figure 4) related to gate a1 to the first server 4. In this case, in step S10, the first server 4 (first control unit 30) generates a building material ID 001 corresponding to the building material data related to gate a1 received by the first server 4, associates gate a1 (building material name data), image a1 of gate a1 (building material image data), gate (building material category data), manufacturer A (building material manufacturer data), height 100cm (building material specification data), and 200,000 yen (building material price data) with the generated building material ID 001, and stores these in the building material DB.
[0064] Figure 8 is a flowchart showing the process executed between the proposer's terminal 1, the second server 5, and the requester's terminal 2.
[0065] The process shown in Figure 8 includes the process of storing (registering) new case data that is not yet stored in the case database. As shown in the figure, the proposer terminal 1 sends new case data (case name data, requester data, requester email address) to the second server 5 based on a request to register new case data (case name data, requester data, requester email address) in the case database (step S21). When the second server 5 receives the case data sent from the proposer terminal 1 (step S22), the second control unit 50 executes the process of registering the received case data in the case database (case registration process) (step S30).
[0066] Figure 9 is a flowchart showing the case registration process (step S30).
[0067] As shown in Figure 9, the second control unit 50 first generates a case ID corresponding to the case data received in step S22 (step S31), then generates a second URL corresponding to the case data received in step S22 (step S32), then associates the case ID generated in step S31 with the case data received in step S22 (case name data, client data, client email address) and the second URL generated in step S32, and stores these in the case DB (step S33), and finally sends the second URL stored in step S33 to the client email address stored in step S33 (step S34), thereby terminating the case registration process.
[0068] For example, case ID 001 shown in Figure 6 is a case ID generated in step S31 when the second server 5 receives the case name data "New Construction of Y1", the client data "Y1", and the client email address "xxx@xx" in step S22.
[0069] In this embodiment, in step S32 (Figure 9), a second URL corresponding to the case data received in step S22 is generated. In other words, a second URL is generated for each case that identifies the request from the client. As mentioned above, the second URL generated in step S32 is for the client to view the building material data proposed by the proposer for each client.
[0070] Figure 10 is a flowchart showing the process executed between the proposer's terminal 1 and the second server 5.
[0071] The process shown in Figure 10 includes the process of displaying a list of case data stored in the case database in the first display area 1a. As shown in the figure, the proposer terminal 1 requests the second server 5 to view a list of case data stored in the case database based on the proposer's operation (for example, the operation of logging the proposer terminal 1 into the second server 5) (step S41). When the second server 5 receives the request from the proposer terminal 1 to view the list of case data, the second control unit 50 first accesses the case database and extracts all case name data from the case data stored in the case database (step S42), and then sends the case name data extracted in step S42 to the proposer terminal 1 (step S43). When the proposer terminal 1 receives the case name data sent from the second server 5, it displays screen G1, which includes the list of received case name data, in the first display area 1a (step S44).
[0072] Figure 11 is a schematic diagram showing an example of screen G1.
[0073] As shown in Figure 11, screen G1 includes area G11. Area G11 is the area that displays the case name data received by the proposer terminal 1 in step S43 (Figure 10).
[0074] The example of screen G1 shown in Figure 11 is an example where the case database stores case data corresponding to case id001 (see Figure 6) and case data corresponding to case id002 (see Figure 6). As shown in the figure, area G11 contains a case column G12 showing case name data corresponding to case id001 (new construction of Y1) and a case column G13 showing case name data corresponding to case id002 (renovation of Y2).
[0075] In this embodiment, the proposer can select case fields G12 and G13 using the input device of the proposer terminal 1.
[0076] Figure 12 is a flowchart showing the process executed between the proposer's terminal 1 and the second server 5.
[0077] The process shown in Figure 12 includes the process of viewing one case data stored in the case database. As shown in the figure, the proposer terminal 1 requests the second server 5 to view the case data corresponding to a case field (hereinafter referred to as "selected case data") located on screen G1, based on the operation of selecting a case field (for example, case field G12) located on screen G1 (step S51). When the second server 5 accepts the request to view the selected case data, the second control unit 50 accesses the case database and extracts the selected case data from the case data stored in the case database (step S52). The second control unit 50 temporarily stores the case ID corresponding to the selected case data extracted in step S52 in the second storage unit 40 (step S53). The second control unit 50 transmits the selected case data extracted in step S52 to the proposer terminal 1 (step S54). When the proposer terminal 1 receives the selected case data transmitted from the second server 5, it displays screen G2 containing this selected case data in the first display area 1a (step S55). In other words, the screen G2 displayed in the first display area 1a in step S55 includes case data (selected case data) corresponding to the case ID temporarily stored in the second storage unit 40 in step S53.
[0078] For example, when an operation is performed to select case field G12 (Figure 11), the second control unit 50 first extracts case data corresponding to case field G12 (selected case data) from the case DB (step S52), then temporarily stores the case id 001 corresponding to the extracted selected case data in the second storage unit 40 (step S53), and finally transmits the case data corresponding to case id 001 to the proposer terminal 1 (step S54). As a result, the proposer terminal 1 displays screen G2 containing the case data corresponding to case id 001 (selected case data) in the first display area 1a (step S55).
[0079] For example, when the user selects case field G13 (Figure 11), the second control unit 50 first extracts the case data corresponding to case field G13 (step S52), then temporarily stores the case ID 002 corresponding to the extracted case data in the second storage unit 40 (step S53), and finally transmits the case data corresponding to case ID 002 to the proposer terminal 1 (step S54). As a result, the proposer terminal 1 displays screen G2 containing the case data (selected case data) corresponding to case ID 002 in the first display area 1a (step S55).
[0080] The case ID stored in step S53 remains stored in the second storage unit 40 until the second control unit 50 extracts the case data in step S52. In other words, the case ID stored in step S53 remains stored in the second storage unit 40 until the proposer requests to view the selected case data. When the proposer requests to view the selected case data, the case ID temporarily stored in the second storage unit 40 is deleted from the second storage unit 40, and in its place, the case ID corresponding to the selected case data related to the viewing request is temporarily stored in the second storage unit 40.
[0081] In the following explanation, the case ID temporarily stored in the second storage unit 40 in step S53 is referred to as the "selected case ID".
[0082] Figure 13 is a schematic diagram showing an example of screen G2.
[0083] Screen G2 includes buttons Ga, Gb, Gc, and area G21.
[0084] Button Ga is used to display screen G1 in the first display area 1a. Button Gb is used to display screen G3 (details described later) in the first display area 1a. Button Gc is used to display screen G6 (details described later) in the first display area 1a. Area G21 is the area for displaying selected case data.
[0085] The screen G2 shown in Figure 13 is an example of the screen G2 that appears in the first display area 1a when the proposer selects the case field G12 (Figure 11) located on screen G1. In other words, the screen G2 shown in Figure 13 is an example of the screen G2 that appears in the first display area 1a when the selected case ID is case ID 001, and this screen G2 corresponds to case ID 001. In short, the screen G2 shown in Figure 13 is the screen G2 that corresponds to case Y1. As shown in the same figure, the area G21 displays the case data corresponding to case ID 001 ("New Construction for Y1", "Y1", "xxx@xx", "httpxx" (see Figure 6)).
[0086] As a variation of this embodiment, screen G2, which corresponds to the selected case ID, may be provided with input fields for entering information such as the date the request was received from the client corresponding to the selected case ID, the date a meeting was held with the client, the date the construction work on the building requested by the client will commence, the date the construction work is scheduled to be completed, the cost required for the request, and other information. The system may be configured to input each of the information corresponding to these input fields based on the proposer's actions, and the information entered in each input field may be linked to the case data corresponding to screen G2 (stored in the case database).
[0087] Thus, in this embodiment, the proposer can view the case data (selected case data) corresponding to a single case field (selected case ID) by selecting a single case field located on screen G1.
[0088] Figure 14 is a flowchart showing the processes executed between the proposer terminal 1, the second server 5, and the first server 4.
[0089] The process shown in Figure 14 includes the process of displaying all or part of the building material data (first building material data) stored in the building material DB in the first display area 1a. As shown in the figure, the proposer terminal 1 requests the second server 5 to view the first building material data based on the operation of selecting button Gb located on screen G2 (step S61). When the second server 5 receives the request to view the first building material data, the second control unit 50 first identifies the selected case ID temporarily stored in the second storage unit 40 (step S62), and then requests the first server 4 to extract all or part of the first building material data depending on whether or not the second building material ID (details described later) is associated with the selected case ID (step S63). When the first server 4 receives a request to extract the first building material data, the first control unit 30 first accesses the building material DB and extracts all or part of the first building material data from the building material DB (step S64), and then transmits the extracted first building material data to the second server 5 (step S65). When the second control unit 50 receives the first building material data transmitted from the first server 4, it transmits the received first building material data and the case name data corresponding to the selected case ID identified in step S62 to the proposer terminal 1 (step S66). When the proposer terminal 1 receives the first building material data and case name data transmitted from the second server 5, it displays screen G3, which includes the received first building material data and case name data, in the first display area 1a (step S67).
[0090] In the following explanation, the building material data displayed in the first display area 1a in step S67 will be referred to as the "second building material data".
[0091] As will be described in more detail later, in this embodiment, the number of building material data displayed on screen G3 (second building material data displayed by the first display means 51 in the first display area 1a) can be reduced based on the proposer's operation. If the number of building material data placed on screen G3 is reduced, the system is configured to request the first server 4 to extract a portion of the first building material data in step S63.
[0092] Figure 15 is a schematic diagram showing an example of screen G3.
[0093] Screen G3 includes buttons Ga, Gb, Gc, area G31, indicator G32, button G33, and button G34.
[0094] Area G31 is the area that displays the project name data sent to the proposer terminal 1 in step S66. Sign G32 is a sign that displays the second building material data. Button G33 is a button to display screen G4 (details described later). Button G34 is a button to display screen G7 (details described later).
[0095] The screen G3 shown in Figure 15 is an example of the screen G3 displayed in the first display area 1a when the proposer selects button Gb located on screen G2 (Figure 13) corresponding to project Y1. In other words, the screen G3 shown in Figure 15 is an example of the screen G3 displayed in the first display area 1a when the selected project ID is project ID 001, and this screen G3 corresponds to project ID 001. That is, the screen G3 shown in Figure 15 is the screen G3 corresponding to project Y1. As shown in the figure, the project name data "New Construction of Y1" (see Figure 6) corresponding to project ID 001 is displayed in area G31.
[0096] The marker G32 is rectangular in shape. One marker G32 displays one second building material data. In the example screen G3 shown in Figure 15, six markers G32 corresponding to gates a1 to a6 are arranged on screen G3. For example, the marker G32 corresponding to gate a1 displays at least building material image data (not shown) related to gate a1.
[0097] The proposer can change the sign G32 placed on screen G3 by using the input device of proposer terminal 1 to scroll screen G3 up and down. This allows the proposer to view all of the building material data sent to proposer terminal 1 in step S66 (Figure 14).
[0098] In this embodiment, screen G3 corresponds to the selected case ID, and the sign G32 placed on screen G3 is configured to be selectable. By performing the operation of selecting sign G32 (an operation to select building material data), the proposer can propose the building material data corresponding to the selected sign G32 to the client related to the selected case ID corresponding to screen G33 on which this sign G32 is placed. In short, screen G3 corresponds to one case, and the proposer can propose building materials to the client of that case by performing the operation of selecting sign G32.
[0099] In this embodiment, a button G33 is placed on screen G3, and by the proposer selecting button G33, screen G4 is displayed in the first display area 1a. The proposer is configured to reduce the number of signs G32 placed on screen G3, i.e., the number of second building material data, via screen G4.
[0100] Detailed explanation and illustration of the process for displaying screen G4 in the first display area 1a are omitted, but based on the operation of selecting button G33, the proposer terminal 1 requests the second server 5 to display screen G4 in the first display area 1a, and when the second server 5 accepts the request to display screen G4, the second control unit 50 transmits data related to screen G4 to the proposer terminal 1, and when the proposer terminal 1 receives the data related to screen G4, it displays screen G4 in the first display area 1a.
[0101] Figure 16 is a schematic diagram showing an example of screen G4.
[0102] As shown in Figure 16, screen G4 includes area G41, area G42, and button G43.
[0103] Area G41 is the area that displays the manufacturers that provide the building material data (first building material data) stored in the building material database that you want to display on screen G3. Area G42 is the area that displays the manufacturers that provide the building material data (first building material data) that you do not want to display on screen G3. Button G43 is a button for changing the number of indicators G32 that are placed on screen G3.
[0104] In the following explanation, manufacturers categorized under area G41 are referred to as "displayed manufacturers," and manufacturers categorized under area G42 are referred to as "hidden manufacturers."
[0105] The example shown in Figure 16 illustrates a case where building material data provided by manufacturers A through E is stored in the building material database, and the proposer uses the input device of proposer terminal 1 to allocate manufacturers A and B to area G41, and manufacturers C, D, and E to area G42. In other words, Figure 16 shows an example where the proposer narrows down (reduces) the marker G32 (second building material data) placed on screen G3 to only the building material data provided by manufacturers A and B.
[0106] Figure 17 is a flowchart showing the process executed between the proposer's terminal 1 and the second server 5.
[0107] The process shown in Figure 17 includes a process to reduce the number of second building material data. As shown in the figure, the proposer terminal 1 sends data related to the display manufacturer to the second server 5 based on the operation of selecting button G43 located on screen G4 (step S71). When the second control unit 50 receives the data related to the display manufacturer sent by the second server 5 in step S71, it first accesses the building material DB and identifies the building material ID corresponding to this data from the building material DB (step S72), then identifies the selected case ID temporarily stored in the second storage unit 40 (step S73), and finally associates the building material ID identified in step S72 with the selected case ID identified in step S72 (step S74). As will be described in detail later, only the building material data corresponding to the building material ID associated with the selected case ID in step S74 is displayed on screen G3.
[0108] In the following explanation, the operation in which the proposer reduces the number of signs G32 (building material data displayed on screen G3) placed on screen G3 via screen G4 is referred to as a "customization operation." Also, the building material ID linked to the selected case ID in step S74 is referred to as the "second building material ID."
[0109] Figure 18 is a diagram illustrating an example of case data stored in the case database.
[0110] Figure 18 shows an example where, in a case where six building material data entries (see Figure 4) are stored in the building material DB, the number of building material data entries (second building material data) displayed on screen G3 is reduced from six to three through a customization operation. More specifically, in step S72, building material id001 (see Figure 4) corresponding to gate a1 provided by manufacturer A, building material id002 (see Figure 4) corresponding to gate a2 provided by manufacturer B, and building material id005 (see Figure 4) corresponding to gate a5 provided by manufacturer A are identified. In step S73, case id001 is identified, and in step S74, building material id001, id002, and id005 are associated with case id001. As shown in Figure 18, second building material id001, id002, and id005 are associated with case id001.
[0111] Figure 19 is a schematic diagram showing an example of screen G3.
[0112] The screen G3 shown in Figure 19 is an example of screen G3 corresponding to case id001 (selected case id), that is, screen G3 corresponding to case Y1, and is an example where second building material id001, id002, and id005 are associated with case id001. In other words, the screen G3 shown in Figure 19 is an example where the proposer has customized screen G4 to display only the building material data provided by manufacturers A and B on screen G3.
[0113] Here, the process of displaying screen G3 shown in Figure 19 in the first display area 1a will be explained with reference to Figure 14. When the proposer terminal 1 requests the second server 5 to view the first building material data based on the operation of selecting button Gb located on screen G2 corresponding to case Y1 (step S61), the second control unit 50 first identifies the selected case id 001 (step S62), and then requests the first server 4 to extract all or part of the building material data from the first building material data (step S63). At this time, as shown in Figure 18, since the second building material id is associated with the selected case id 001 identified in step S62, in step S63, the first server 4 is requested to extract some of the building material data from the first building material data. Specifically, the first server 4 is requested to extract only the building material data corresponding to the second building material ids 001, id 002, and id 005 associated with the selected case id 001 identified in step S62. Detailed explanations of the processes from step S64 onward are omitted, but the first control unit 30 extracts only the building material data corresponding to the second building material ids 001, 002, and 005 from the building material DB (step S64), and sends these to the second server 5 (step S65). The second control unit 50 then sends the building material data corresponding to the second building material ids 001, 002, and 005, along with the project name data (New Construction of Y1) corresponding to the selected project id 001, to the proposer terminal 1 (step S66). As a result, the proposer terminal 1 displays screen G3 shown in Figure 19 in the first display area 1a (step S67).
[0114] Comparing screen G3 shown in Figure 15 with screen G3 shown in Figure 19, both screens correspond to case id001 (case Y1), but they differ in that screen G3 in Figure 15 displays six indicators G32 corresponding to gates a1 through a6, while screen G3 in Figure 19 displays only three indicators G32 corresponding to gates a1, a2, and a5.
[0115] Thus, in this embodiment, the number of second building material data displayed on screen G3 can be reduced by the proposer's operation for each case ID, that is, for each case that identifies a request from the client.
[0116] Figure 20 is a magnified view of marker G32.
[0117] The indicator G32 includes element G32a. Element G32a indicates whether or not it is building material data proposed by the proposer to the client. Element G32a is normally white, and changes from white to black when element G32a is selected.
[0118] Figure 20(a) shows that element G32a is white, indicating that the proposer did not select element G32a. In other words, the proposer did not propose building material data corresponding to Figure 20(a) to the client.
[0119] Figure 20(b) shows that element G32a is black, indicating that the proposer has selected element G32a. In other words, the proposer is proposing building material data corresponding to Figure 20(b) to the client.
[0120] Thus, screen G3, which corresponds to the selected case ID, is configured to display all or some of the building material data stored in the building material database according to the customization operation. The proposer can select the building material data they wish to propose to the client corresponding to the selected case ID by performing the operation of selecting element G32a (second building material data) of the sign G32 placed on screen G3.
[0121] In the following explanation, the process by which the proposer selects building material data from the second set of building material data that they wish to propose to the client is referred to as the "pickup operation." The building material data selected through the pickup operation is referred to as the "third set of building material data."
[0122] Figure 21 is a flowchart showing the process executed between the proposer's terminal 1 and the second server 5.
[0123] The process shown in Figure 21 includes the process of associating the building material data selected in the pickup operation with the case ID. As shown in the figure, the proposer terminal 1 transmits the building material data (third building material data) selected in the pickup operation to the second server 5 (step S81). When the second control unit 50 receives the building material data transmitted by the second server 5 in step S81, it first identifies the building material ID corresponding to the received building material data (step S82), then identifies the selected case ID temporarily stored in the second storage unit 40 (step S83), and finally associates the building material ID identified in step S82 with the selected case ID identified in step S83 (step S84).
[0124] In the following explanation, the building material ID linked to the selected project ID in step S84 will be referred to as the "third building material ID".
[0125] Figure 22 is a schematic diagram showing an example of screen G3.
[0126] The screen G3 shown in Figure 22 is an example of screen G3 corresponding to case id001 (case Y1), and is an example of screen G3 displayed in the first display area 1a when gate a1 and gate a5 are selected as building materials to be proposed to Y1 through the pick-up operation.
[0127] Although not shown in the illustration, the second control unit 50 first identifies the building material id001 (see Figure 4) corresponding to gate a1 and the building material id005 (see Figure 4) corresponding to gate a5 in step S82, then identifies the case id001 (selected case id001) in step S83, and finally associates the building material id001 (third building material id001) and the building material id005 (third building material id005) as third building material data with the case id001 in step S83.
[0128] Figure 23 is a diagram illustrating an example of case data stored in the case database.
[0129] The example of project data shown in Figure 23 is an example of what happens when the pickup operation shown in Figure 22 (screen G3) is performed. In other words, the example in Figure 23 shows the project data corresponding to project id001 when the proposer performs a pickup operation to select gate a1 and gate a5 as building materials to propose to Y1. As shown in the figure, project id001 is associated with third building material id001 and third building material id005.
[0130] Figure 24 is a flowchart showing the process executed between the client terminal 2 and the second server 5.
[0131] The process shown in Figure 24 includes the process of displaying the third building material data (building material data corresponding to the building material selected by the proposer to propose to the client) in the second display area 2a. As shown in the figure, the client terminal 2 requests the second server 5 to view the third building material data based on the client's operation of specifying the second URL (the second URL sent to the email address used by the client in step S34 of Figure 9) (step S91). When the second control unit 50 receives the client's request to view the third building material data, it first accesses the case DB and identifies the case ID corresponding to the second URL from the case DB (step S92), then identifies the third building material data corresponding to the case ID identified in step S92 (the building material ID related to the third building material data associated with the case ID) (step S93), and finally sends the case name data corresponding to the case ID identified in step S92 and the third building material data identified in step S93 to the client terminal 2 (step S94). When the client terminal 2 receives the project name data and the third building material data transmitted from the second server 5, it displays screen G5, which includes the received project name data and the third building material data, in the second display area 2a (step S95).
[0132] Figure 25 is a schematic diagram showing an example of screen G5.
[0133] Screen G5 includes area G51 and indicator G52.
[0134] Area G51 is the area where the case name (case name data transmitted in step S94) corresponding to the selected case data (selected case ID) is displayed. Marker G52 is a marker that displays the third building material data (third building material data transmitted in step S94). One third building material data is displayed per marker G52.
[0135] The screen G5 shown in Figure 25 corresponds to case id001 (Y1 case). In other words, the screen G5 shown in the figure is an example of the screen G5 that is displayed in the second display area 2a when Y1 specifies the second URL sent to the email address used by Y1. As shown in the figure, the screen G5 has signs G52 corresponding to building material id001 (gate a1) and signs G52 corresponding to building material id005 (gate a5). This indicates that the proposer has selected the building material corresponding to gate a1 and the building material corresponding to gate a5 as the building materials to propose to Y1 (see Figures 22 and 23).
[0136] Figure 26 is a magnified view of marker G52.
[0137] The indicator G52 includes element G52a. Element G52a indicates whether the building material data meets the client's preferences and desires. Element G52a is normally white, and changes from white to black when element G51a is selected.
[0138] Figure 26(a) shows that the color of element G52a is white, indicating that the client did not select element G52a. In other words, the building material data corresponding to Figure 26(a) is building material data that does not meet the client's preferences or desires.
[0139] Figure 26(b) shows that the color of element G52a is black, indicating that the client has selected element G52a. In other words, the building material data corresponding to Figure 26(b) is building material data that suits the client's preferences and desires.
[0140] Thus, in this embodiment, the client can select building material data that suits their preferences and desires from among the third building material data displayed on screen G5 by selecting element G52a using the input device of the client terminal 2.
[0141] In the following explanation, the operation in which the proposer selects building material data that suits their preferences and desires from the third set of building material data will be referred to as the "favorite selection operation." Furthermore, the building material data selected through the favorite selection operation will be referred to as the "fourth set of building material data."
[0142] Figure 27 is a flowchart showing the process executed between the client terminal 2 and the second server 5.
[0143] The process shown in Figure 27 includes the process of associating the building material ID corresponding to the building material data selected in the favorite selection operation with the case ID. As shown in the figure, the client terminal 2 sends the building material data corresponding to the sign G52 selected in the favorite selection operation to the second server 5 (step S101). When the second control unit 50 receives the building material data sent by the second server 5 in step S101, it first identifies the building material ID corresponding to the received building material data (step S102), then identifies the selected case ID temporarily stored in the second storage unit 40 (step S103), and finally associates the building material ID identified in step S102 with the selected case ID identified in step S103 (step S104).
[0144] In the following explanation, the building material ID linked to the selected project ID in step S104 will be referred to as the "fourth building material ID".
[0145] Figure 28 is a schematic diagram showing an example of screen G5.
[0146] The screen G5 shown in Figure 28 is an example of a screen G5 that is displayed in the second display area 2a when one of the two signs G52, which corresponds to gate a1, is selected by the favorite selection operation.
[0147] Although not shown in the diagram, when the favorite selection operation shown in Figure 28 is performed, the second control unit 50 first identifies the building material id001 (see Figure 4) corresponding to gate a1 in step S102, then identifies the case id001 (selected case id001) in step S103, and finally associates the building material id001 (fourth building material id001) with the case id001 as fourth building material data in step S104.
[0148] Figure 29 is a diagram illustrating an example of case data stored in the case database.
[0149] The example shown in Figure 29 is an example of case data stored in the case database when the favorite selection operation shown in Figure 28 is performed. Specifically, it is an example where, due to the favorite selection operation by Y1, the building material corresponding to gate a1 is selected, and the building material id001 (fourth building material id001) corresponding to gate a1 is associated with case id001.
[0150] Figure 30 is a flowchart showing the process executed between the proposer's terminal 1 and the second server 5.
[0151] The process shown in Figure 30 includes the process of displaying the fourth building material data in the first display area 1a. As shown in the figure, the proposer terminal 1 requests the second server 5 to view the fourth building material data based on the operation of selecting a button Gc located on screen G2 or screen G3 (step S111). When the second server 5 receives the request to view the fourth building material data, the second control unit 50 first identifies the selected case ID temporarily stored in the second storage unit 40 (step S112), then accesses the case DB to identify the fourth building material data associated with the selected case ID identified in step S112 (step S113), and finally sends the fourth building material data identified in step S113 and the case name data corresponding to the selected case ID identified in step S112 to the proposer terminal 1 (step S114). When proposer terminal 1 receives the fourth building material data and project name data transmitted from the second server 5, it displays screen G6, which includes the received fourth building material data and project name data, in the first display area 1a (step S115).
[0152] Figure 31 is a schematic diagram showing an example of screen G6.
[0153] As shown in Figure 31, screen G6 includes regions G61 and G62.
[0154] Area G61 is the area that displays the case name (case name data sent in step S114) corresponding to the selected case data (selected case ID). Area G62 is the area that displays the building material data (fourth building material data) selected by the client in the favorite selection operation, that is, the fourth building material data sent in step S114.
[0155] The screen G6 shown in Figure 31 corresponds to case id001 (Y1 case). In other words, the screen G6 shown in Figure 31 displays the fourth building material data selected by Y1 in the favorite selection operation. As shown in the figure, area G61 displays the case name data (Y1's new construction) corresponding to case id001, and area G62 displays some of the building material data (gate a1, manufacturer A, 200,000 yen) corresponding to building material id001 (fourth building material id001).
[0156] Figure 32 is a magnified view of marker G32.
[0157] The indicator G32 includes element G32b. Element G32b indicates whether or not it is building material data to be used in the project. Element G32b is normally white, and changes from white to black when selected by the proposer.
[0158] Figure 32(a) shows that the color of element G32b is white, indicating that the proposer did not select element G32b. In other words, the building material data corresponding to Figure 32(a) is building material data that will not be used in the project.
[0159] Figure 32(b) shows that element G32b is black, indicating that the proposer has selected element G32b. In other words, the building material data corresponding to Figure 32(b) is the building material data to be used in the project.
[0160] Thus, in this embodiment, the proposer can select element G32b using the input device of the proposer terminal 1, thereby setting the building material data to be used for the project from the third building material data (building material data selected by the pickup operation) displayed on screen G3.
[0161] In the following explanation, the operation in which the proposer selects the building material data to be used in the project from the third building material data will be referred to as the "usage setting operation." The building material data set through the usage setting operation will be referred to as the "fifth building material data."
[0162] Figure 33 is a flowchart showing the process executed between the proposer's terminal 1 and the second server 5.
[0163] The process shown in Figure 33 includes the process of setting the building materials to be used for a project. As shown in the figure, the client terminal 1 transmits building material data corresponding to the sign G32 selected in the usage setting operation to the second server 5 based on the operation (step S121). When the second control unit 50 receives the building material data transmitted by the second server 5 in step S121, it first identifies the building material ID corresponding to the received building material data (step S122), then identifies the selected project ID temporarily stored in the second storage unit 40 (step S123), and finally associates the building material ID identified in step S122 with the selected project ID identified in step S123 (step S124).
[0164] In the following explanation, the building material ID linked to the selected project ID in step S124 will be referred to as the "fifth building material ID".
[0165] Figure 34 is a schematic diagram showing an example of screen G3.
[0166] Figure 34 shows screen G3 corresponding to project id001 (Project Y1), and is an example of screen G3 when the proposer selects element G32b of sign G32 corresponding to gate a1 in Project Y1. In other words, screen G3 shown in the figure indicates that the proposer has decided to use gate a1 as a building material in the project related to the new construction of Y1 (Project Y1).
[0167] To explain Figure 34 in more detail, the screen G3 shown in the figure displays three building material data (three signs G32; three second-tier building material data) from the building material database through a customization operation. Two of these three building material data (two signs G32) are selected through a pickup operation, and then one of the two selected building material data (two third-tier building material data) is set through a usage setting operation.
[0168] Once the usage setting operation shown in Figure 34 is performed, the second control unit 50 first identifies the building material id001 (see Figure 4) corresponding to gate a1 in step S122, then identifies the case id001 in step S123, and finally associates the building material id001 (fifth building material id001) as fifth building material data with the case id001 in step S124.
[0169] Figure 35 is a diagram illustrating an example of case data stored in the case database.
[0170] The example of case data shown in Figure 35 is an example of what happens when the usage setting operation shown in Figure 34 is performed. As shown in the figure, case id001 is associated with building material id001 (number 5).
[0171] Figure 36 is a flowchart showing the process executed between the proposer's terminal 1 and the second server 5.
[0172] The process shown in Figure 36 includes the process of displaying the fifth building material data in the first display area 1a. As shown in the figure, the proposer terminal 1 requests the second server 5 to view the fifth building material data based on the operation of selecting button G34 located on screen G3 (see Figure 34, etc.) (step S131). When the second server 5 receives the request to view the fifth building material data, the second control unit 50 first identifies the selected case ID temporarily stored in the second storage unit 40 (step S132), then identifies the fifth building material data associated with the selected case ID identified in step S132 (step S133), and finally transmits the fifth building material data identified in step S133 and the case name data corresponding to the selected case ID identified in step S132 to the proposer terminal 1 (step S134). When proposer terminal 1 receives the fifth building material data and project name data transmitted from the second server 5, it displays screen G7 containing these in the first display area 1a (step S135).
[0173] Figure 37 is a schematic diagram showing an example of screen G7.
[0174] As shown in Figure 37, screen G7 includes area G71, area G72, and button G73.
[0175] Area G71 is the area that displays the case name data corresponding to the selected case ID sent to the proposer terminal 1 in step S134. Area G72 is the area for displaying the building material data (fifth building material data) selected by the proposer in the usage setting operation. Button G73 is the button for sending (providing) the fifth building material data to the client corresponding to the selected case ID sent to the proposer terminal 1 in step S134.
[0176] The example of screen G7 shown in Figure 37 is screen G7 corresponding to project id001 (Y1 project), and area G72 contains building material data corresponding to gate a1. In other words, screen G7 in Figure 37 is a screen that indicates that it has been set (decided) to use the building materials for gate a1 for the project related to the new construction of Y1, which was requested by Y1.
[0177] Figure 38 is a flowchart showing the process executed between the proposer terminal 1, the second server 5, and the requester terminal 2.
[0178] The process shown in Figure 38 includes the process of sending (providing) fifth building material data to the client. As shown in the figure, the proposer terminal 1 requests the second server 5 to send the fifth building material data to the client based on the operation of selecting button G73 located on screen G7 (step S141). When the second server 5 receives the request to send the fifth building material data, the second control unit 50 first identifies the selected case ID temporarily stored in the second storage unit 40 (step S142), then identifies the fifth building material data associated with the selected case ID identified in step S142 (step S143), then identifies the client email address associated with the selected case ID identified in step S142 (step S144), and finally sends the fifth building material data identified in step S143 to the client email address identified in step S144 (step S145). The client can use the client terminal 2 to display the fifth building material data sent from the second server 5 in the second display area 2a.
[0179] Incidentally, manufacturers of building materials currently commercialize a vast variety and number of building materials, and create catalogs containing information about these materials (design, price, specifications, etc.) in paper or electronic format. These catalogs, created in paper or electronic format (hereinafter referred to as "paper catalogs"), are produced individually by each manufacturer, and their formats are not uniform but inconsistent.
[0180] House builders and other proposers receive consultations from clients planning new construction or exterior work regarding building, remodeling, and repairs. Based on the client's preferences and desired building materials, which the proposer has gathered from the aforementioned paper catalogs, they create a document summarizing these selected materials and propose it to the client, thereby obtaining orders for construction, etc. However, as mentioned above, paper catalogs have inconsistent formats and contain a vast number of building materials, posing a challenge for proposers as they have to expend considerable effort creating proposals for clients.
[0181] On the other hand, when clients are planning to build a house, for example, they tend to consult with multiple house builders (proposers) rather than limiting themselves to just one. The client then selects one of these proposers and commissions them to construct the building. As a result, it is difficult for house builders and other proposers to secure orders from all clients who come to them for consultation, and improving their order rate remains a challenge.
[0182] In this embodiment, the second server 5 (first display means 51) controls the display of building material data (first building material data) stored in the building material DB of the first server 4 in the first display area 1a based on a request from the proposer (step S61 in Figure 14) (step S67 in Figure 14). In other words, the proposer does not need to specify a first URL to view the first building material data; they can view the first building material data by accessing the second server 5. This streamlines the proposer's work and reduces their workload.
[0183] In this embodiment, based on a request from the proposer (step S71 in Figure 17), the number of building material data (second building material data) displayed on screen G3 (the number of building material data displayed by the first display means 51 in the first display area 1a) can be reduced. This allows the proposer to reduce the workload of viewing building material data by pre-decreasing the number of building material data displayed on screen G3.
[0184] In particular, in this embodiment, the number of second building material data can be reduced for each case. More specifically, as shown in Figure 17, when a request is received to reduce the number of building material data displayed on screen G3 corresponding to a certain case (step S71), the system is configured to associate the case ID (selected case ID) corresponding to the case in the case DB with the building material ID (second building material ID shown in Figure 18) corresponding to the building material data (for example, data related to the display manufacturer) that the proposer has selected to display on screen G3 (step S74). As shown in Figure 14, when a request is received to view the building material data (first building material data) stored in the building material DB via screen G2 (screen G3) corresponding to a certain case (step S61), only the building material data from the building material DB that corresponds to the second building material ID associated with the case ID (selected case ID) corresponding to the case is displayed in the first display area 1a of the proposer terminal 1 (step S67). In short, the system SY according to this embodiment associates one project data (selected project data) selected by the proposer from the project data stored in the project DB with a second building material data (second building material data) selected by the proposer from the building material data stored in the building material DB, and controls the system to display the second building material data associated with the project data in the first display area 1a. This makes it possible to display only building materials suitable for the project on screen G3, taking into account the actual circumstances of the project. For example, in a project related to new construction by client Y1, only building materials from manufacturers A and B, which provide a large supply of building materials to the market, can be displayed on screen G3. For example, in a project related to renovation by client Y2, only building materials for the part to be renovated can be displayed on screen G3. This makes it possible to display only building materials suitable for the project on screen G3, taking into account the actual circumstances of the project, and makes it easier to select building materials to propose to the client.
[0185] It goes without saying that in this embodiment, after reducing the number of building material data displayed on screen G3, the number can be increased via screen G4. In other words, the support system SY according to this embodiment can also be said to be equipped with an increasing means that increases the number of building material data displayed in the first display area 1a by the proposer's operation.
[0186] In this embodiment, it is possible to increase or decrease the number of building material data displayed in the first display area 1a for each project without increasing or decreasing the number of building material data stored in the building material DB, thus making it highly versatile.
[0187] In this embodiment, the second building material data displayed on screen G3 (sign G32 placed on screen G3) is configured to be selectable, and the proposer can select the building materials they wish to propose to the client by performing a pickup operation to select the second building material data (an operation to select element G32a of sign G32) (Figures 21 and 22). Therefore, the proposer does not need to produce a conventional paper catalog for the client, nor does they need to edit the building material data to create an image data catalog to propose to the client. This significantly reduces the proposer's workload.
[0188] In this embodiment, the second control unit 50 (second display means 53) displays only the building material data (third building material data) selected by the proposer through a pickup operation on the second display area 2a of the client terminal 2, based on the client's request (step S91 in Figure 24) (step S95 in Figure 24). As a result, the client can view the building materials (third building material data) proposed (selected) by the proposer via the client terminal 2 without actually visiting the proposer, and does not need to look through the vast number of paper catalogs provided by manufacturers, etc. This reduces the effort required of the client to consider the specifications of the building.
[0189] In this embodiment, when registering (storing) case data related to a new request in the case database, the second control unit 50 is configured to generate a second URL corresponding to the case data to be registered and send the generated second URL to the client email address used by the corresponding client (step S34 in Figures 8 and 9). In other words, the proposer can provide the second URL to the client simply by registering the case data in the case database. This reduces the workload of the proposer and prevents the generated second URL from being mistakenly sent to the wrong client's email address.
[0190] In this embodiment, the building material data (third building material data) displayed on screen G5 is configured to be selectable, and the client can select their preferred building material data by performing a favorite selection operation (step S101 in Figure 27) to select the third building material data (Figures 27 and 28). For example, before the proposer and the client discuss the specifications of the building, the proposer can provide the client with the building materials they wish to propose via the system SY, and the client can select their preferred building materials from those proposed by the proposer via the system SY. This reduces the workload for both the proposer and the client, shortens the time from the request to the construction of the building, and improves the order acceptance rate for requests.
[0191] In this embodiment, the second control unit 50 (first display means 51) displays only the building material data (fourth building material data) selected by the client in the favorite selection operation in the first display area 1a based on the proposer's request (step S111 in Figure 30) (step S115 in Figure 30, Figure 31), so that the proposer can easily understand the client's preferred building materials.
[0192] In this embodiment, the building material data (second building material data) displayed on screen G3 is configured to be selectable, and the proposer can set the building material data (fifth building material data) to be used in the project by performing a usage setting operation (an operation to select element G32b) to select the second building material data (Figures 33 and 34). This reduces the proposer's workload.
[0193] In particular, in this embodiment, the indicator G32 placed on screen G3 includes elements G32a and G32b, where element G32a indicates whether or not it is building material data (third building material data) proposed by the proposer to the client, and element G32b indicates whether or not it is building material data (fifth building material data) to be used in the project. That is, the system SY according to this embodiment includes a building material DB for storing building material data, a project DB for storing project data, a first display means 51 for displaying one indicator G32 corresponding to one building material data stored in the building material DB in the first display area 1a of the proposer terminal 1, and a reduction means 52 for reducing the number of indicators G32 displayed by the first display means 51 in the first display area 1a by operation of the proposer, where one indicator G32 includes element G32a indicating that it is building material data selected (proposed) by the proposer for a client relating to a project corresponding to one of the project data stored in the project DB, and element G32b indicating whether or not it is building material data to be used in the project. Therefore, sign G32 can show the proposer both the building materials that the proposer proposed (selected) for the client and the building materials that the proposer decided to use in the project (Figure 34).
[0194] In this embodiment, by selecting button G34 located on screen G3, screen G7 containing the building material data set in the usage setting operation is displayed in the first display area 1a (step S135 in Figure 36). By selecting button G73 located on screen G7, the fifth building material data can be provided to the client (Figures 37 and 38). This eliminates the need to create a document containing only the building materials used in the project, thereby reducing the proposer's workload.
[0195] In this embodiment, as shown in Figure 16, the number of building material data displayed on screen G3 is reduced by performing an operation (customization operation) to allocate manufacturers providing building materials to either area G41 or area G42. However, the configuration is not limited to this. For example, a screen may be prepared in advance that allows the user to set gates and mailboxes as building material data to be displayed on screen G3, and other building material data belonging to other building material categories not to be displayed on screen G3. The number of building material data (second building material data) displayed on screen G3 can then be reduced by the proposer's operation on this screen. Similarly, a screen may be prepared in advance that allows the user to set gates and mailboxes below a certain price as building material data to be displayed on screen G3, and other building material data not to be displayed on screen G3. The number of building material data displayed on screen G3 can then be reduced by the proposer's operation on this screen.
[0196] Furthermore, as a variation of this embodiment, the display order of the building material data displayed on screen G3 may be changed.
[0197] Figure 39 is a schematic diagram showing a modified version of screen G4.
[0198] The example shown in Figure 39 is an example of the screen when, in a case where building material data corresponding to building materials provided by manufacturers A through D is stored in the building material database, the proposer uses the input device of proposer terminal 1 to operate the screen G3 so that manufacturer A is displayed first, then manufacturer B, then manufacturer C, and finally manufacturer D.
[0199] In the above modified example, as shown in Figure 39, the display order (display configuration) of the building material data displayed on screen G3 is changed by arranging the manufacturers providing the building materials from top to bottom. Therefore, the display order (display configuration) of the building material data displayed on screen G3 can be changed for each project without increasing or decreasing the number of building material data stored in the building material database.
[0200] Furthermore, the modifications described above are not the only possible variations. The display order (display configuration) of the building material data (second building material data) displayed on screen G3 may be changed by performing operations to arrange building material categories (see Figure 4; for example, categories such as gates and mailboxes), building material name data, or building material price data.
[0201] Furthermore, it goes without saying that by combining screen G4 according to this embodiment (Figure 16) with screen G4 according to the modified example (Figure 39), it is possible to change both the number of building material data displayed in the first display area 1a and the display order (display pattern) of the building material data displayed on screen G3 for each project, without increasing or decreasing the number of building material data stored in the building material DB.
[0202] In this embodiment, the system SY includes a first server 4 and a second server 5, with the first server 4 having a building materials database and the second server 5 having a case database. However, the system is not limited to this configuration. For example, the system SY may include only the second server 5, and the second server 5 may have both a case database and a building materials database. Even with this configuration, the number of building materials data displayed in the first display area 1a can be changed for each case without reducing the number of building materials data stored in the building materials database.
[0203] In this embodiment, a button Gc is placed on screen G3, and based on the operation of selecting button Gc, the second control unit 50 (first display means 51) is configured to display screen G7 in the first display area 1a, which includes only the building material data (fourth building material data) selected by the favorite selection operation. However, the configuration is not limited to this, and a configuration in which the fourth building material data is displayed on screen G3 is also possible. A modified example of this will be described below.
[0204] Figure 40 is a schematic diagram showing a modified version of screen G3.
[0205] As shown in Figure 40, screen G3 displays the third building material data selected by the pick-up operation (two markers G32 corresponding to gates a1 and a5, including the black element G32a), the fourth building material data selected by the favorite selection operation (one marker G32 corresponding to gate a1, including the black element G32c), and the fifth building material data set by the usage setting operation (one marker G32 corresponding to gate a1, including the black element G32b).
[0206] By viewing screen G3 shown in Figure 40, the proposer can see at a glance that they proposed gate a1 and gate a5 to the client out of the three building materials related to gate a1, gate a2, and gate a5, that the client selected gate a1 as their preferred building material out of gate a1 and gate a5, and that the proposer set gate a1 as the building material to be used in the project.
[0207] The system, programs, etc., in this embodiment can be modified in various ways without altering the essence of the present invention. Furthermore, the control sequence can also be modified as appropriate, provided that it achieves a predetermined effect.
[0208] <Configuration 1> The support system SY according to this embodiment is a support system that assists proposers who propose building specifications to clients, and comprises a second control unit 50 (control unit) and a first storage unit 20 (storage unit), wherein the first storage unit 20 stores building material data (specification data) related to building specifications, and the second control unit 50 is characterized by including a first display means 51 that displays the building material data stored in the first storage unit 20 in a first display area 1a of the proposer terminal 1, a reduction means 52 that reduces the number of building material data displayed by the first display means 51 in the first display area 1a by the proposer's operation, and a second display means 53 that displays only the building material data selected by the proposer's operation from the building material data displayed by the first display means 51 in the second display area 2a of the client terminal 2.
[0209] <Configuration 2> The first server 4 and the second server 5 according to this embodiment are support devices that assist a proposer in proposing building specifications to a client, and include a second control unit 50 (control unit) and a first storage unit 20 (storage unit), wherein the first storage unit 20 stores building material data (specification data) related to the building specifications, and the second control unit 50 is characterized by including a first display means 51 that displays the building material data stored in the first storage unit 20 in a first display area 1a of the proposer terminal 1, a reduction means 52 that reduces the number of building material data displayed by the first display means 51 in the first display area 1a by the proposer's operation, and a second display means 53 that displays only the building material data selected by the proposer's operation from the building material data displayed by the first display means 51 in the second display area 2a of the client terminal 2.
[0210] <Structure 3> This is a support method for a proposer who proposes building specifications to a client, and is characterized by including the steps of: S67 (Figure 14) of displaying building material data (specification data) related to the building specifications stored in the first storage unit 20 in the first display area 1a of the proposer terminal 1 based on the proposer's request; S74 (Figure 17) of reducing the number of building material data displayed in the first display area 1a based on the proposer's request; S84 (Figure 21) of selecting building material data to propose to the client from the building material data displayed in the first display area 1a based on the proposer's request; and S95 (Figure 24) of displaying only the building material data selected based on the proposer's request in the second display area 2a of the client terminal 2 based on the client's request.
[0211] <Structure 4> The second control unit 50 is characterized by including a modification means (not shown) that allows the proposer to change the display mode of the building material data displayed by the first display means 51 in the first display area 1a.
[0212] <Composition 5> The first display means 51 is characterized by displaying in the first display area 1a building material data (fourth building material data) selected by the client from among the building material data displayed in the second display area 2a by the second display means 53 (Figure 31).
[0213] <Composition 6> The first display means 51 is characterized by displaying in the first display area 1a, in a manner that allows the proposer to identify the building material data selected by the client (fourth building material data) from among the building material data displayed in the second display area 2a by the second display means 53, and the building material data that was not selected (Figure 40).
[0214] In this embodiment, the example of "building materials" was used to explain the specifications of a building proposed by the proposer to the client. However, the same configuration applies to "exterior of the building" and "interior of the building" as to the specifications of a building proposed by the proposer to the client. Therefore, their illustrations and detailed explanations have been omitted. Below, a brief explanation will be given using the configuration of "exterior of the building" as an example.
[0215] Furthermore, floor plans vary considerably depending on the shape of the building and are not uniform like building materials or the exterior of a building. For this reason, floor plans are not suitable as building specifications proposed by the proposer via the SY system. Therefore, the proposer shall not propose floor plans to the client via the SY system, and in the invention according to this embodiment, floor plans shall not be included in the building specifications.
[0216] <Composition 7> The support system SY according to this embodiment is a support system that assists proposers who propose building specifications to clients, and comprises a second control unit 50 (control unit) and an appearance DB (storage unit), wherein the appearance DB stores building appearance data (specification data), and the second control unit 50 is characterized by including a first display means 51 that displays the appearance data stored in the appearance DB in a first display area 1a of the proposer terminal 1, a reduction means 52 that reduces the number of appearance data displayed by the first display means 51 in the first display area 1a by the proposer's operation, and a second display means 53 that displays only the appearance data selected by the proposer's operation from the appearance data displayed by the first display means 51 in the first display area 1a in the second display area 2a of the client terminal 2.
[0217] <Structure 8> The first server 4 and the second server 5 according to this embodiment are support devices that assist a proposer in proposing building specifications to a client, and include a second control unit 50 (control unit) and an appearance DB (storage unit), wherein the appearance DB stores building appearance data (specification data), and the second control unit 50 is characterized by including a first display means 51 that displays the appearance data stored in the appearance DB in a first display area 1a of the proposer terminal 1, a reduction means 52 that reduces the number of appearance data displayed by the first display means 51 in the first display area 1a by the proposer's operation, and a second display means 53 that displays only the appearance data selected by the proposer from the appearance data displayed by the first display means 51 in the first display area 1a in the second display area 2a of the client terminal 2.
[0218] <Composition 9> This is a support method for a proposer who proposes building specifications to a client, and is characterized by including the steps of: displaying building exterior data (specification data) related to the building specifications stored in the exterior DB in a first display area 1a of the proposer terminal 1 based on the proposer's request; reducing the number of exterior data displayed in the first display area 1a based on the proposer's request; selecting exterior data to propose to the client from the exterior data displayed in the first display area 1a based on the proposer's request; and displaying only the exterior data selected based on the proposer's operation in a second display area 2a of the client terminal 2 based on the client's request.
[0219] <Composition 10> The second control unit 50 is characterized by including a modification means that allows the proposer to change the display mode of the appearance data displayed by the first display means 51 in the first display area 1a.
[0220] <Composition 11> The first display means 51 is characterized by displaying in the first display area 1a the appearance data selected by the client from among the appearance data displayed in the second display area 2a by the second display means 53.
[0221] <Composition 12> The first display means 51 is, The second display means 53 displays in the second display area 2a the appearance data selected by the client's operation and the appearance data that was not selected, in the first display area 1a in a manner that the proposer can identify. [Explanation of Symbols]
[0222] SY System 1. Proposer's terminal 1a 1st display area 2. Client terminal 2a 2nd display area 4. First Server (Support Device) 5. Second Server (Support Device) 20 1st memory section (storage section) 50 Second Control Unit (Control Unit) 51 First display means 52 Reduction means 53 Second display means
Claims
1. A support system that assists proposers who propose building specifications to clients, It comprises a control unit and a memory unit, The aforementioned storage unit stores specification data related to the specifications of the building. The control unit, A first display means that displays the specification data stored in the storage unit in the first display area of the terminal used by the proposer, A reduction means for reducing the number of specification data displayed in the first display area by the proposer's operation, The system includes a second display means that displays only the specification data selected by the proposer's operation from the specification data displayed in the first display area of the first display means in the second display area of the terminal used by the client. A support system characterized by the following features.
2. A support device for a proposer who proposes building specifications to a client, It comprises a control unit and a memory unit, The aforementioned storage unit stores specification data related to the specifications of the building. The control unit, A first display means that displays the specification data stored in the storage unit in the first display area of the terminal used by the proposer, A reduction means for reducing the number of specification data displayed in the first display area by the proposer's operation, The system includes a second display means that displays only the specification data selected by the proposer's operation from the specification data displayed in the first display area of the first display means in the second display area of the terminal used by the client. A support device characterized by the following features.
3. A support method for assisting proposers who propose building specifications to clients, Based on the request of the proposer, the step of displaying specification data relating to the specifications of the building stored in the storage unit on the first display area of the terminal used by the proposer, Based on the request of the proposer, the steps include reducing the number of specification data to be displayed in the first display area, Based on the request of the proposer, the step of selecting specification data to propose to the client from the specification data displayed in the first display area, The step of displaying only the specification data selected based on the request of the proposer, based on the request of the client, in the second display area of the terminal used by the client. A support method characterized by the following features.
Citation Information
Patent Citations
JP121585A
JP134685A
Method and mechanism for controlling pressure in processing chamber
JP1993006227A