Dwelling unit sales management device, dwelling unit sales management method, and dwelling unit sales management program

Abstract

To provide a dwelling unit sales management device that, in dwelling unit sales, can create sales forecasts linked to delivery schedules, and analyze the sales of dwelling units, the reservation contract status, and the status grasp and transition of monthly sales progress from the start of contracts.SOLUTION: A dwelling unit sales management device according to a present embodiment includes: a first master that has registered a sales price of each dwelling unit number for each property; contract processing means for registering contract information data including a contract number, a project, a property name, a dwelling unit number, an application date, a contract date, and a scheduled delivery date; and delivery status data processing means for aggregating the contract information data on a year / month basis for each property in the project, and for creating and outputting delivery status data including delivery dwelling units that are scheduled to be delivered as of a relevant year / month, delivered dwelling units that have already been delivered, yet-to-be-delivered dwelling units, the number of vacant dwelling units that are yet contracted dwelling units as of the relevant year / month, and a sales amount obtained by aggregating the sales prices of the delivery dwelling units with reference to the first master.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a dwelling unit sales management device, a dwelling unit sales management method, and a dwelling unit sales management program. [Background technology]

[0002] For example, in condominium sales, there are many cases where the delivery date is delayed due to contract changes or external factors, and it is not possible to accurately grasp the collection schedule until the delivery is confirmed. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-95972 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, Patent Document 1 does not state anything about creating a sales forecast (e.g., based on the number of units and amount) linked to the scheduled delivery date for selling residential units, understanding the status and trends of residential unit sales, reservation contract status, and monthly sales progress from the start of the contract, and analyzing the trends.

[0005] The present invention has been made in consideration of the above, and aims to provide a dwelling unit sales management device, a dwelling unit sales management method, and a dwelling unit sales management program that are capable of creating a sales forecast linked to delivery plans in dwelling unit sales, and grasping and analyzing the status and trends of dwelling unit sales, reservation contract status, and monthly sales progress from the start of a contract. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides an apartment sales management device equipped with a control unit, the control unit being configured to be able to access a first master in which the sales price of each apartment number for each property is registered, and is characterized in being equipped with: a contract processing means for registering contract information data including a contract number, project, property name, apartment number, application date, contract date, and scheduled delivery date; and a delivery status data processing means for aggregating the contract information data by year and month for each property of the project, and creating and outputting delivery status data including the number of apartments to be delivered whose delivery date is scheduled as of that year and month, apartments that have already been delivered, apartments that are not yet delivered, and vacant apartments that are not yet contracted as of that year and month, and the sales amount obtained by aggregating the sales prices of the apartments to be delivered by referring to the first master.

[0007] According to one aspect of the present invention, the delivery status data processing means may create and output delivery status data for all properties of the project, based on the delivery status data, by aggregating all properties of the project by month and year, including the number of delivered dwelling units, sales amount, cumulative sales amount which is the accumulated amount of sales amounts up to a specified month and year, and a delivery rate calculated by: total delivered dwelling units / total number of dwelling units x 100.

[0008] According to one embodiment of the present invention, the control unit may be configured to be able to access a second master in which a target amount for each project is registered, and may be equipped with a project-specific transition processing means for creating and outputting project-specific transition data based on the delivery status data of all properties in the project, the data including the number of delivered dwelling units, cumulative sales amount, delivery rate, and achievement rate calculated by cumulative sales amount / target amount for the project in the second master x 100, for each project and by year and month.

[0009] According to another aspect of the present invention, the dwelling unit may include an apartment building or a detached house.

[0010] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides an apartment sales management method executed by an information processing device equipped with a control unit, the control unit being configured to be able to access a first master in which the sales price of each apartment number for each property is registered, and the method includes a contract processing step executed by the control unit to register contract information data including the contract number, project, property name, apartment number, application date, contract date, and scheduled delivery date, and a delivery status data processing step to create and output delivery status data for each property in the project by aggregating the contract information data by year and month, and including the number of apartments to be delivered whose delivery date is scheduled as of that year and month, apartments that have already been delivered, apartments that are not yet delivered, and vacant apartments that are not yet contracted for as of that year and month, and the sales amount obtained by aggregating the sales prices of the apartments to be delivered by referring to the first master.

[0011] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention is an apartment sales management program for being executed on an information processing device equipped with a control unit, the control unit being configured to be able to access a first master in which the sales price of each apartment number for each property is registered, and the control unit is configured to execute a contract processing step of registering contract information data including a contract number, project, property name, apartment number, application date, contract date, and scheduled delivery date, and a delivery status data processing step of aggregating the contract information data by year and month for each property in the project, and creating and outputting delivery status data including the number of delivered apartments whose delivery date is scheduled as of that year and month, delivered apartments whose delivery has already been completed, undelivered apartments, and vacant apartments that are not yet contracted for as of that year and month, and the sales amount obtained by aggregating the sales prices of the delivered apartments by referring to the first master. Effect of the Invention

[0012] According to the present invention, in the sale of a residence, it is possible to create a sales forecast linked to the scheduled delivery date, and to grasp and analyze the sales situation of the residence, the reservation contract status, and the monthly sales progress from the start of the contract. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a residence sales management device according to the present embodiment. [Diagram 2] FIG. 2 is a diagram showing an example of the configuration of the property room information master. [Diagram 3] FIG. 3 is a diagram illustrating an example of the configuration of the project goal master. [Figure 4] FIG. 4 is a diagram illustrating an outline of a flow of the overall process of the control unit of the information processing device in this embodiment. [Diagram 5] FIG. 5 is a diagram showing sample data for explaining a specific example of the process of the control unit of the information processing device in this embodiment. [Figure 6] FIG. 6 is a diagram showing sample data for explaining a specific example of the process of the control unit of the information processing device in this embodiment. [Figure 7] FIG. 7 is a diagram showing sample data for explaining a specific example of the process of the control unit of the information processing device in this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the drawings. However, the present invention is not limited to the embodiment.

[0015] [1. Overview] For example, in condominium sales, delays in handover dates due to contract changes or external factors are not uncommon, and it is not possible to accurately grasp the expected recovery time until the handover is confirmed. In addition, in the real estate developer industry, which uses an investment recovery model, management of financial plans is essential, and visualization of expected recovery time is a very important issue. In addition, when deciding how to deal with unsold properties (hold them as they are, rent them out, sell them to a competitor, etc.), it is desirable to be able to analyze them both inside and outside the project.

[0016] Therefore, in this embodiment, a sales forecast (based on number of units and amount) based on the delivery schedule is created, and the collection schedule at the contract stage (not yet delivered) is clarified using the delivery status data. In addition, sales progress and trends are analyzed on a project-by-project basis, and if the properties are not sold out after the project is launched and completed, the subsequent sales, number of remaining properties, and the number of months elapsed are analyzed from the start of the contract.

[0017] This allows you to compare progress and trends on a project-by-project basis, which contributes to planning for individual projects (rentals and sales) as well as for future projects. In addition, because the recovery schedule is clear, it becomes possible to more concretely consider the start date for the next development project.

[0018] The present invention is widely applicable to industries that sell dwelling units, such as the real estate developer industry, the real estate distribution industry, etc. In the following example, condominium sales will be described as an example, but the dwelling unit sales management device of the present invention is applicable not only to condominium sales but also to sales of detached dwelling units, etc.

[0019] [2. Configuration] FIG. 1 is a block diagram showing an example of the configuration of a dwelling unit sales management device 100 according to this embodiment. In FIG. 1, the dwelling unit sales management device 100 is, for example, a commercially available desktop personal computer. The dwelling unit sales management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer. The dwelling unit sales management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each unit included in the dwelling unit sales management device 100 is connected to be able to communicate with each other via an arbitrary communication path.

[0020] The communication interface unit 104 communicatively connects the dwelling sales management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the dwelling sales management device 100 to the server 200 and the bank system 400 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

[0021] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to realize a pointing device function. In the following, the output device 114 may be referred to as a monitor 114.

[0022] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs for cooperating with an OS (Operating System) to give instructions to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. For example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, optical disks, etc. can be used as the storage unit 106.

[0023] The storage unit 106 includes a property room information master (first master) 106a, a project goal master (second master) 106b, and a data file 106c. Fig. 2 is a diagram showing an example of the configuration of the property room information master 106a. Fig. 3 is a diagram showing an example of the configuration of the project goal master 106b.

[0024] The property room information master 106a can be configured as a table or the like in which data on property name, room number, and sales price are registered in association with each other, as shown in Fig. 2. In the example shown in Fig. 2, the first line has the property name "Property A", room number "101", and sales price "40,000,000". The property room information master 106a is linked to the contract information data using the property name and room number as keys, and the sales price is read out using the property name and room number as keys.

[0025] The project goal master 106b can be configured as a table in which project numbers and target amounts are registered in association with each other, as shown in Fig. 3. In the example shown in Fig. 3, the first line has the project number "P001" and the target amount "200,000,000." The target amount is read from the project goal master 106b using the project number as a key.

[0026] The data file 106c is a file for storing various data such as contract information data, delivery status data, delivery status data for all properties in the project, and transition data by project.

[0027] The contract information data may include data such as a contract number, a project number, a property name, a room number, an application date, a contract date, a scheduled delivery date, and a delivery date.

[0028] The delivery status data may include data on the year and month, the number of delivered units, delivered units, undelivered units, and vacant units, the subtotal, and the sales amount. The delivery status data for all properties in the project may include data on the number of delivered units, the sales amount, the cumulative sales amount, and the delivery rate.

[0029] The project-specific trend data may include data on the project number, the number of units delivered, the cumulative sales amount, the delivery rate, and the achievement rate.

[0030] Returning to Fig. 1, the control unit 102 is a CPU or the like that performs overall control of the residence sales management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing operations based on these stored programs.

[0031] The control unit 102 is configured to be able to access the property room information master 106a, the project goal master 106b, the data file 106c, and the like stored in the storage unit 106. Note that the property room information master 106a, the project goal master 106b, and the data file 106c may be provided in another location (e.g., the server 200) as long as the control unit 102 is able to access them.

[0032] The control unit 102 conceptually includes a contract processing unit 102a, a delivery status processing unit 102b, a project-specific transition processing unit 102c, a master maintenance unit 102d, and a screen display control unit 102e.

[0033] The contract processing unit 102a inputs contract information data including the contract (contract number and / or contract name), project (project number and / or project name), property name, room number (apartment number), application date, contract date, and scheduled delivery date, for example, in response to operator operations on an input screen (not shown) displayed on the monitor 114, and registers the data in the data file 106c.

[0034] The delivery status processing unit 102b compiles the contract information data registered in the data file 106c by year and month for each property in the project, and creates delivery status data including the number of delivered dwelling units whose delivery date is scheduled for that year and month, delivered dwelling units that have already been delivered, undelivered dwelling units, and vacant dwelling units that are not under contract for that year and month, as well as the sales amount obtained by tallying up the sales prices of the delivered dwelling units by referring to the property room information master 106a, and registers this data in the data file 106c or displays it on the monitor 114.

[0035] In addition, based on the delivery status data, the delivery status processing unit 102b tallyes up all properties of the project by year and month, and creates delivery status data for all properties of the project, including the number of delivered dwelling units, sales amount, cumulative sales amount which is the accumulated amount of sales amounts up to the specified year and month, and delivery rate calculated by (total delivered dwelling units / total number of dwelling units x 100), and registers this data in the data file 106c or displays it on the monitor 114.

[0036] The project-specific transition processing unit 102c creates project-specific transition data including the number of delivered dwelling units, cumulative sales amount, delivery rate, and achievement rate calculated by multiplying cumulative sales amount by the target amount of the project in the project goal master 106b by 100 for each year and month based on the delivery status data of all properties in the project, and registers the data in a data file 106c or displays it on the monitor 114.

[0037] The master maintenance unit 102d is for performing settings such as inputting, adding, changing, and updating data for the property room information master 106a and the project goal master 106b in response to, for example, an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114.

[0038] The screen display control unit 102f controls the display of various screens (for example, a master maintenance screen, various input screens, various output screens, etc.) displayed on the monitor 114 and the reception of inputs.

[0039] [3. Specific Examples] A specific example of the processing performed by control unit 102 of residence unit sales management device 100 in this embodiment will be described with reference to FIGS.

[0040] (3-1. Overall processing) 4 is a diagram showing a flow for explaining an outline of the overall processing of the control unit 102 of the dwelling unit sales management device 100 in this embodiment. With reference to FIG. 4, an outline of the overall processing of the control unit 102 of the dwelling unit sales management device 100 in this embodiment will be explained.

[0041] 4, the master maintenance unit 102d executes a master maintenance process (step S1). Specifically, in the master maintenance process, the master maintenance unit 102d sets data of the property room information master 106a and the project goal master 106b in response to, for example, an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114.

[0042] The contract processing unit 102a executes a contract information data registration process (step S2). Specifically, in the contract information data registration process, for example, in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, contract information data including a contract number, a project, a property name, a dwelling unit number, an application date, a contract date, and a scheduled delivery date are input and registered in the data file 106c.

[0043] The delivery status processing unit 102b executes a delivery status data creation process (step S3). Specifically, in the delivery status data creation process, the delivery status processing unit 102b aggregates the contract information data registered in the data file 106c for each property of the project by year and month, creates delivery status data including the number of delivered dwelling units whose delivery date is scheduled as of the relevant year and month, delivered dwelling units whose delivery has already been completed, undelivered dwelling units, and vacant dwelling units that are not under contract as of the relevant year and month, and the sales amount obtained by aggregating the sales prices of the delivered dwelling units by referring to the property room information master 106a, and registers the data in the data file 106c or displays the data on the monitor 114.

[0044] In addition, in the delivery status data creation process, the delivery status processing unit 102b tallyes up all properties in the project by year and month based on the above delivery status data, creates delivery status data for all properties in the project, including the number of delivered dwelling units, sales amount, cumulative sales amount which is the accumulated amount of sales amounts up to the specified year and month, and delivery rate calculated by total delivered dwelling units / total number of dwelling units x 100, and registers the data in the data file 106c or displays it on the monitor 114.

[0045] The project-specific transition processing unit 102c executes a project-specific transition data creation process (step S4). Specifically, in the project-specific transition data creation process, the project-specific transition processing unit 102c creates project-specific transition data including the number of delivered dwelling units, cumulative sales amount, delivery rate, and achievement rate calculated by cumulative sales amount / target amount of the project in the project target master 106b×100 for each year and month for each project based on the delivery status data of all properties of the project, and registers the data in the data file 106c or displays it on the monitor 114.

[0046] (3-2. Sample data) 5 to 7 are diagrams showing sample data for explaining a specific example of the processing by control unit 102 of dwelling unit sales management device 100 in this embodiment. A specific example of the processing by control unit 102 of dwelling unit sales management device 100 in this embodiment will be explained with reference to Figs. 5 to 7.

[0047] (S1: Master maintenance processing) The master maintenance unit 102d sets data for the property room information master 106a and the project goal master 106b in response to, for example, an operation by an operator on a master maintenance screen (not shown) displayed on the monitor 114.

[0048] Fig. 5(B) is a diagram showing an example of data in the property room information master 106a. In the example of the property room information master 106a shown in Fig. 5(B), the first line contains the property name "Property A", the room number "101", and the selling price "40,000,000". The selling price is read out from the property room information master 106a using the property name and room number as keys.

[0049] Fig. 7(C) is a diagram showing an example of data in the project-goal master 106b. In the example of the project-goal master 106b shown in Fig. 7(C), the first line shows the project number "P001" and the target amount "200,000,000." The target amount is read from the project-goal master 106b using the project number as a key.

[0050] (S2: Contract information data registration process) The contract processing unit 102a inputs contract information data including a contract number, a project number, a property name, a dwelling unit number, an application date, a contract date, and a scheduled delivery date, for example, in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, and registers the data in a data file 106c.

[0051] (1) Register contract information data. Fig. 5(A) is a diagram showing an example of contract information data. In Fig. 5(A) showing an example of contract information data, the first line contains contract number "K001", project number "P001", property name "Property A", room number "101", application date "020 / 04 / 10", contract date "2020 / 04 / 21", and scheduled delivery date "2020 / 10 / 31". Here, an example for project number "P001" is shown, but contract information data is also registered for project numbers "P002" and "P003".

[0052] (S3: Delivery status data creation process) The delivery status processing unit 102b compiles the contract information data registered in the data file 106c by year and month for each property in the project, and creates delivery status data including the number of delivered dwelling units whose delivery date is scheduled for that year and month, delivered dwelling units that have already been delivered, undelivered dwelling units, and vacant dwelling units that are not under contract for that year and month, as well as the sales amount obtained by tallying up the sales prices of the delivered dwelling units by referring to the property room information master 106a, and registers this data in the data file 106c or displays it on the monitor 114.

[0053] Here, "delivered units" refer to units for which delivery has already been completed as of that year / month (not including deliveries in the current month). "Delivered units" are used to manage how many deliveries have occurred out of the total number of rooms. "Undelivered units" are used to manage units that have been contracted as of that year / month and are scheduled to be delivered in the future. "Vacant units" refer to units that have not yet been contracted as of that year / month. By registering this information at the time of contracting, it is possible to predict trends from the present to the future.

[0054] (2) Delivery status data is created based on the dates stored in the contract information data. Contract information data is compiled by year and month, and the number of contracts is obtained according to each condition, from vacant units to delivered units. The sales amount is calculated only when the unit is delivered. In addition, the year and month are extracted from the minimum and maximum values ​​of the target contract information data. The sales amount is calculated by obtaining the sales price from the property room information master 106a using the property name and room number as keys and compiling it.

[0055] Figure 5(C) shows an example of delivery status data, indicating the delivery status of property name "Property A" in project "P001". In the example of delivery status data in Figure 5(C), for the year and month "2020 / 4", the number of delivered units is "0", delivered units is "0", undelivered units is "1", vacant units is "7", subtotal is "8", and sales amount is "0". For the year and month "2020 / 4", contract number "K001" in the contract information data was concluded in 2020 / 4 and is scheduled to be delivered in 2020 / 10, so at this point in time, the number of undelivered units is "1".

[0056] For the year and month "2020 / 5", the following are the delivered units: "0", delivered units: "0", undelivered units: "2", vacant units: "6", subtotal: "8", and sales amount: "0". For the year and month "2020 / 5", the contract information data's contract number "K002" was concluded in 2020 / 5 and is scheduled for delivery in 2020 / 10, so at this point, the number of undelivered units is "2".

[0057] For the year and month "2020 / 8", the following are the delivered units: "0", delivered units: "0", undelivered units: "3", vacant units: "5", subtotal: "8", and sales amount: "0". For the year and month "2020 / 8", the contract information data's contract number "K003" was concluded in 2020 / 8 and is scheduled to be delivered in 2020 / 11, so at this point, the number of undelivered units is "3".

[0058] For the year and month "2020 / 10", the following are the delivered units: "0", delivered units: "2", undelivered units: "1", vacant units: "5", subtotal: "8", and sales amount: "0". Since the contract information data contract numbers "K001, K002" are scheduled for delivery in 2020 / 10, the delivered units are set to "2". The sales amount is calculated as "40,000,000" for the property name "Property A" and room number "101" in the property room information master 106a for the contract number "K001" in the contract information data + "30,000,000" for the property name "Property A" and room number "102" in the property room information master 106a for the contract number "K002" in the contract information data = "70,000,000".

[0059] For the year and month "2020 / 11", the following are the delivered units: "2", delivered units: "1", undelivered units: "0", vacant units: "5", subtotal: "8", and sales amount: "70,000,000". Since contract number "K003" in the contract information data is scheduled for delivery in 2020 / 11, the delivered units are listed as "1", and the cumulative total of past delivered units is listed as the delivered units, so the delivered units are listed as "2" (contract numbers "K001, K002").

[0060] Furthermore, based on the delivery status data, the delivery status processing unit 102b tallyes up all properties of the project by year and month, and creates delivery status data for all properties of the project, including the number of delivered dwelling units, sales amount, cumulative sales amount which is the accumulated amount of sales amounts up to the specified year and month, and delivery rate calculated by (total delivered dwelling units / total number of dwelling units x 100), and registers this data in the data file 106c or displays it on the monitor 114.

[0061] (3) The delivery status data created in (2) is managed for each project, and delivery status data for all properties in the project is created. Figure 6 is a diagram showing an example of delivery status data for all properties in a project, and shows an example of the progress (based on number and amount) of all properties in project "P001". The example shown in Figure 6 includes items such as year and month, delivered units, sales amount, delivered units, accumulated sales amount, and delivery rate. Accumulated sales amount is the accumulated amount of sales amount up to the specified year and month. The delivery rate is calculated by total delivered units / total number of units x 100.

[0062] Although an example for project number "P001" is shown here, delivery status data is also created for project numbers "P002" and "P003."

[0063] (S4: Project-specific transition data creation process) The project-specific transition processing unit 102c creates project-specific transition data including the number of delivered dwelling units, cumulative sales amount, delivery rate, and achievement rate calculated by multiplying cumulative sales amount by the target amount of the project in the project goal master 106b by 100 for each year and month based on the delivery status data of all properties in the project, and registers the data in a data file 106c or displays it on the monitor 114.

[0064] (4) Based on the delivery status data of all properties of the project created in (3), project-specific transition data is created to manage the data on a project-by-project basis. In this case, a project goal master 106b is prepared in which a target amount is set for each project, so that the achievement rate can also be confirmed. The achievement rate is calculated by cumulative sales amount / target amount of the project in the project goal master 106b x 100.

[0065] Fig. 7(A) shows an example of contract information data, and also includes examples of project numbers "P002, P003". Fig. 7(B) shows an example of the property room information master 106a. Fig. 7(C) shows an example of the project goal master 106b.

[0066] Figure 7(D) shows an example of project-specific transition data. In the example shown in Figure 7(D), for project number "P001", in October 2020, the number of delivered units is "2", the cumulative sales amount is "70,000,000", the delivery rate is "25%", and the achievement rate is "35%". In November 2020, the number of delivered units is "3", the cumulative sales amount is "120,000,000", the delivery rate is "38%", and the achievement rate is "60%". In December 2020, the number of delivered units is "3", the cumulative sales amount is "120,000,000", the delivery rate is "38%", and the achievement rate is "60%".

[0067] For project number "P002," in October 2020, the number of delivered units is "1," the cumulative sales amount is "30,000,000," the delivery rate is "33%," and the achievement rate is "50%." In November 2020, the number of delivered units is "1," the cumulative sales amount is "30,000,000," the delivery rate is "33%," and the achievement rate is "50%." In December 2020, the number of delivered units is "1," the cumulative sales amount is "30,000,000," the delivery rate is "33%," and the achievement rate is "50%."

[0068] For project number "P003," in October 2020, the number of delivered units is "2," the cumulative sales amount is "80,000,000," the delivery rate is "50%," and the achievement rate is "50%." In November 2020, the number of delivered units is "3," the cumulative sales amount is "120,000,000," the delivery rate is "75%," and the achievement rate is "75%." In December 2020, the number of delivered units is "4," the cumulative sales amount is "160,000,000," the delivery rate is "100%," and the achievement rate is "100%."

[0069] More specific information can be provided by comprehensively checking and comparing the above-mentioned (2) delivery status data for each property in the project, (3) delivery status data for all properties in the project, and (4) trends in project-specific data.

[0070] For example, for project number "P002", there is no increase in the number of deliveries within the project. (2) The delivery status data for each property in project number "P002" and (3) the transition of the delivery status data for all properties in project "P002" make it possible to check the progress of each property, which can be used as material for policy decisions such as holding, renting, or selling. It is also possible to automatically pick up properties whose delivery rate has not reached 100%.

[0071] For project number "P003," both the number of deliveries and the cumulative sales amount are increasing within the project. Comparing project information and trends can provide useful information for planning the next project.

[0072] As described above, according to this embodiment, the system includes the property room information master 106a in which the sales price of each dwelling unit number for each property is registered, the contract processing unit 102a in which contract information data including the contract number, project, property name, dwelling unit number, application date, contract date, and scheduled delivery date, and the delivery status processing unit 102b in which the contract information data is compiled by year and month for each property of the project, and the delivery status data including the number of dwelling units to be delivered whose delivery date is scheduled as of the relevant year and month, dwelling units that have already been delivered, dwelling units that have not yet been delivered, and vacant dwelling units that are not yet contracted as of the relevant year and month, and the sales amount obtained by compiling the sales prices of the dwelling units to be delivered by referring to the property room information master 106a, and therefore, in the case of dwelling unit sales, it is possible to analyze the status and trends of dwelling unit sales, reservation contract status, and monthly sales progress from the start of the contract and analyze the trends.

[0073] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to goals 8 and 9 of the SDGs.

[0074] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0075] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[0076] 5. Other embodiments The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0077] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0078] In addition, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

[0079] Moreover, with regard to the dwelling unit sales management device 100, the components shown in the figures are merely functional concepts, and the device does not necessarily have to be physically configured as shown in the figures.

[0080] For example, the processing functions of the dwelling unit sales management device 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that includes programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the dwelling unit sales management device 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into a RAM, and cooperates with the CPU to form the control unit.

[0081] In addition, this computer program may be stored in an application program server connected to the residence unit sales management device 100 via any network, and it is also possible to download all or part of it as necessary.

[0082] In addition, the program for executing the process described in this embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.

[0083] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration as multiple modules or libraries, and a program that works with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, may use well-known configurations and procedures.

[0084] The various databases etc. stored in the memory unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files etc. used for various processes and providing websites.

[0085] The dwelling unit sales management device 100 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as the information processing device to which any peripheral device is connected. The dwelling unit sales management device 100 may be realized by installing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

[0086] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Explanation of symbols]

[0087] 100 Residence sales management device 102 Control section 102a Contract Processing Department 102b Delivery Status Processing Unit 102c Project-specific transition processing section 102d Master Maintenance Department 102e Screen display control unit 104 Communication interface section 106 Storage section 106a Property room information master 106b Project Objective Master 106c Data File 108 Input / Output Interface Section 112 Input Devices 114 Output Device 300 Network

Claims

1. A residence sales management device having a control unit, The control unit is The system is configured to be able to access a first master in which the sales price of each dwelling unit number for each property is registered, A contract processing means for registering contract information data including a contract number, a project, a property name, a dwelling unit number, an application date, a contract date, and a scheduled delivery date; a delivery status data processing means for creating and outputting delivery status data including the number of dwelling units to be delivered that are scheduled to be delivered as of that year and month, dwelling units that have already been delivered, dwelling units that have not yet been delivered, and vacant dwelling units that are not under contract as of that year and month, and the sales amount obtained by aggregating the sales prices of the dwelling units to be delivered by referring to the first master; A residence sales management device comprising:

2. The residence sales management device of claim 1, characterized in that the delivery status data processing means creates and outputs delivery status data for all properties of the project, including the number of delivered residences, sales amount, cumulative sales amount which is the accumulated amount of sales amounts up to the specified year and month, and delivery rate calculated by total delivered residences / total number of residences x 100, based on the delivery status data.

3. The control unit is The second master in which the target amount for each project is registered is accessible. The dwelling unit sales management device as described in claim 2, characterized in that it is characterized by having a project-specific transition processing means for creating and outputting project-specific transition data including the number of delivered dwelling units, cumulative sales amount, delivery rate, and achievement rate calculated by cumulative sales amount / target amount of the project in the second master x 100, by project and by year and month, based on the delivery status data of all properties in the project.

4. 4. The dwelling unit sales management device according to claim 1, wherein the dwelling unit includes an apartment or a detached house.

5. A method for managing sales of a residence executed by an information processing device having a control unit, The control unit is The system is configured to be able to access a first master in which the sales price of each dwelling unit number for each property is registered, Executed in the control unit: a contract processing step of registering contract information data including a contract number, a project, a property name, a dwelling unit number, an application date, a contract date, and a scheduled delivery date; a delivery status data processing step for creating and outputting delivery status data including the number of dwelling units to be delivered that are scheduled to be delivered as of that year and month, dwelling units that have already been delivered, dwelling units that have not yet been delivered, and vacant dwelling units that are not under contract as of that year and month, and the sales amount calculated by aggregating the sales prices of the dwelling units to be delivered by referring to the first master; A method for managing the sale of a residence, comprising:

6. A residence sales management program to be executed by an information processing device having a control unit, The control unit is The system is configured to be able to access a first master in which the sales price of each dwelling unit number for each property is registered, In the control unit, a contract processing step of registering contract information data including a contract number, a project, a property name, a dwelling unit number, an application date, a contract date, and a scheduled delivery date; a delivery status data processing step for creating and outputting delivery status data including the number of dwelling units to be delivered that are scheduled to be delivered as of that year and month, dwelling units that have already been delivered, dwelling units that have not yet been delivered, and vacant dwelling units that are not under contract as of that year and month, and the sales amount calculated by aggregating the sales prices of the dwelling units to be delivered by referring to the first master; A residential sales management program to implement the above.

Images